| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "SQL sentence"? |
| Date: | 2017-02-18 04:36:23 |
| Message-ID: | cf3ce85d-4bd5-4b5f-059a-484c4038a2b8@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/17/17 10:19 PM, Alvaro Herrera wrote:
>> (FWIW, I'm wondering because I was just looking to see why there's no
>> details for things like altering a column in a table.)
> Do you mean you want to have access to the details of the alter table
> operations being executed? There's no structured data for that; you
> need to write a C function to examine the pg_ddl_command opaque column.
Yeah. It doesn't seem unreasonable for a user to want to get at that info.
Could the opaque column be mapped to a composite? I guess that'd be a
bit of a pain due to the union. :/ And I have a suspicion that
alterTable.subcmds is a list of CollectedCommand, making things more fun.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2017-02-18 04:36:30 | Re: pg_get_object_address() doesn't support composites |
| Previous Message | Alvaro Herrera | 2017-02-18 04:19:23 | Re: "SQL sentence"? |