Re: Unsafe coding in ReorderBufferCommit() - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Unsafe coding in ReorderBufferCommit()
Date
Msg-id 20150126105205.GA9916@awork2.anarazel.de
Whole thread Raw
In response to Unsafe coding in ReorderBufferCommit()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Unsafe coding in ReorderBufferCommit()
List pgsql-hackers
Hi Tom,

On 2015-01-23 16:47:30 -0500, Tom Lane wrote:
> There are at least two bugs in reorderbuffer.c's ReorderBufferCommit():

Thanks for fixing these!

Unfortunately there's more - we'll currently do bad things if
transaction commit fails. At the very least the (sub-)transaction begin
commands need to be moved out of the exception block as they can
fail... :(. E.g. because this is the 2^32-1 subxact or similar...

I actually also want to strip the CATCH block of most of it's contents -
there's really no need anymore for most of what it does.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe?
Next
From: Andres Freund
Date:
Subject: Re: longjmp clobber warnings are utterly broken in modern gcc