On 2/17/17 10:46 PM, Alvaro Herrera wrote:
Sure. We have the extension that turned the command into JSON. It's
still an unfinished patch, sadly, even though Alex Shulgin spent a lot
of effort trying to get it finished. It is still missing a nontrivial
amount of work, but within reach ISTM.
On 2/17/17 10:46 PM, Alvaro Herrera wrote:
Jim Nasby wrote:
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
Jim Nasby wrote:
> 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
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
Jim Nasby wrote:
> I'm confused by this:
>
> "pg_event_trigger_ddl_commands returns one row for each base command
> executed; some commands that are a single SQL sentence may return more than
> one row."
>
> What is a "SQL sentence"?
I meant "a single SQL command". The word "sentence" probably
