| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | depstein <depstein(at)alliedtesting(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, pgagarinov <pgagarinov(at)alliedtesting(dot)com> |
| Subject: | Re: pg_upgrade issues |
| Date: | 2010-07-26 16:18:06 |
| Message-ID: | 201007261618.o6QGI6L12336@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera wrote:
> Excerpts from depstein's message of lun jul 26 08:05:24 -0400 2010:
>
> > I just want to note that one reason regclass may be used in user tables (as opposed to, say, regtype) is that in PL/pgSQL trigger procedures there is a special variable TG_RELID, which provides a convenient reference to the table that pulled the trigger (this is the case for some of our uses).
>
> I've wanted to use regclass (and regproc too, for that matter) in some
> db designs, but I've refrained precisely because of the movability
> issues.
Were you worried about pg_upgrade movability issues, or just general
movability issues?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2010-07-26 16:49:08 | Re: page corruption after moving tablespace |
| Previous Message | Alvaro Herrera | 2010-07-26 14:56:21 | Re: pg_upgrade issues |