| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | depstein <depstein(at)alliedtesting(dot)com> |
| Cc: | bruce <bruce(at)momjian(dot)us>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, pgagarinov <pgagarinov(at)alliedtesting(dot)com> |
| Subject: | Re: pg_upgrade issues |
| Date: | 2010-07-26 14:56:21 |
| Message-ID: | 1280156084-sup-9446@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
Note that you can use TG_SCHEMANAME and TG_RELNAME in plpgsql triggers
anyway.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-07-26 16:18:06 | Re: pg_upgrade issues |
| Previous Message | Tizziano Perea | 2010-07-26 14:25:49 | BUG #5572: Error Trying to connec from Crystal Reports to Sever PostgreSQL |