Re: Table rewrites vs. pending AFTER triggers - Mailing list pgsql-hackers

From Gokulakannan Somasundaram
Subject Re: Table rewrites vs. pending AFTER triggers
Date
Msg-id 9362e74e0801022304k1fc31f3fwcc7b6cd4bd629d4a@mail.gmail.com
Whole thread Raw
In response to Re: Table rewrites vs. pending AFTER triggers  (Andrew Dunstan <adunstan@postgresql.org>)
Responses Re: Table rewrites vs. pending AFTER triggers
Re: Table rewrites vs. pending AFTER triggers
List pgsql-hackers
Is there why we allow DDLs inside a transaction and allow it to be rolled back? If we commit the previous transaction, as soon as we encounter a DDL, and commit the DDL too (without waiting for commit) will it be affecting some use cases?

I actually mean to say that DDLs can be declared as self-committing. That would get rid of these exceptions.

Am i missing something?

Thanks,
Gokul.

On Jan 3, 2008 12:02 AM, Andrew Dunstan < adunstan@postgresql.org> wrote:


Simon Riggs wrote:
> On Tue, 2008-01-01 at 16:09 -0500, Tom Lane wrote:
>
>
>> Paranoia would
>> suggest forbidding *any* form of ALTER TABLE when there are pending
>> trigger events, but maybe that's unnecessarily strong.
>>
>
> That works for me. Such a combination makes no sense, so banning it is
> the right thing to do.
>
>

+1. Doesn't make much sense to me either.

cheers

andrew

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

              http://archives.postgresql.org


pgsql-hackers by date:

Previous
From: "Brian Modra"
Date:
Subject: Re: Index performance
Next
From: Tom Lane
Date:
Subject: Re: Table rewrites vs. pending AFTER triggers