Wow Andrew,
Great work! Lot of ideas to pick from.
Now, like you said it looks rather complicated and fragile. We will take a look
at creating a custom C trigger to see if we can have something easier.
Pity there was no agreement to just expose the object that fired the trigger.
Best,
On J
On Mon, Jul 29, 2013 at 10:08 PM, Javier de la Torre wrote:
> You think it will be possible to, instead of comparing schemas, looking
> for the last modified OID on the DB to figure out where it happened?
>
Not really. When a row has been updated, you can only see the new values.
By comparing t
Thanks Andrew,
You think it will be possible to, instead of comparing schemas, looking for the
last modified OID on the DB to figure out where it happened?
On Jul 29, 2013, at 3:42 PM, Andrew Tipton wrote:
> On Mon, Jul 29, 2013 at 9:12 PM, Javier de la Torre
> wrote:
> Hi,
>
> I was look
On Mon, Jul 29, 2013 at 9:12 PM, Javier de la Torre
wrote:
> Hi,
>
> I was looking at the new event triggers on 9.3 and was doing some testing.
> I have compiled PostgreSQL 9.3 Beta2
> It looks from the examples that the only info right now available on
> plpgsql when the triggers fire is tg_event
