On Wed, Oct 9, 2013 at 2:12 AM, Marc Cousin cousinm...@gmail.com wrote:
On Tuesday 08 October 2013 12:28:46 Robert Haas wrote:
On Mon, Oct 7, 2013 at 12:32 PM, Marc Cousin cousinm...@gmail.com wrote:
I was using the lo contrib a few days ago and wasn't paying attention, and
forgot the for
Sawada Masahiko sawada.m...@gmail.com writes:
On Mon, Oct 7, 2013 at 12:32 PM, Marc Cousin cousinm...@gmail.com wrote:
I was using the lo contrib a few days ago and wasn't paying attention, and
forgot the for each row in the create trigger command... PostgreSQL
segfaulted, when the trigger
On Mon, Oct 7, 2013 at 12:32 PM, Marc Cousin cousinm...@gmail.com wrote:
I was using the lo contrib a few days ago and wasn't paying attention, and
forgot the for each row in the create trigger command... PostgreSQL
segfaulted, when the trigger tried to access the row's attributes.
Please
On Tuesday 08 October 2013 12:28:46 Robert Haas wrote:
On Mon, Oct 7, 2013 at 12:32 PM, Marc Cousin cousinm...@gmail.com wrote:
I was using the lo contrib a few days ago and wasn't paying attention, and
forgot the for each row in the create trigger command... PostgreSQL
segfaulted, when the
I was using the lo contrib a few days ago and wasn't paying attention, and
forgot the for each row in the create trigger command... PostgreSQL
segfaulted, when the trigger tried to access the row's attributes.
Please find attached a patch to control that the trigger is correctly defined
(as in
