Andres Freund wrote:
> On 2013-07-19 13:46:44 -0400, Alvaro Herrera wrote:
> > Sadly, this has performance implications, because what previously was
> > just an in-place check of bit flags has now become a function call.
>
> Well, the impact imo primarily comes from actually resolving the
> multi
Andres Freund wrote:
> On 2013-07-19 13:46:44 -0400, Alvaro Herrera wrote:
> > Sadly, this has performance implications, because what previously was
> > just an in-place check of bit flags has now become a function call.
>
> Well, the impact imo primarily comes from actually resolving the
> multi
On 2013-07-19 13:46:44 -0400, Alvaro Herrera wrote:
> levert...@googlemail.com wrote:
>
> > START TRANSACTION ISOLATION LEVEL SERIALIZABLE;
> > CREATE TABLE testing(
> > x INTEGER PRIMARY KEY
> > );
> > INSERT INTO testing VALUES(1);
> > SELECT * FROM testing WHERE x = 1 FOR UPDATE;
> > SAVEPOIN
levert...@googlemail.com wrote:
> START TRANSACTION ISOLATION LEVEL SERIALIZABLE;
> CREATE TABLE testing(
> x INTEGER PRIMARY KEY
> );
> INSERT INTO testing VALUES(1);
> SELECT * FROM testing WHERE x = 1 FOR UPDATE;
> SAVEPOINT test;
> UPDATE testing SET x = 2 WHERE x = 1;
> ROLLBACK TO test;
>
Jeff Janes escribió:
> The bug was introduced in commit: 0ac5ad5... Improve concurrency of foreign
> key locking.
>
> I don't know what more to look into on this, so I'm cc Alvaro, the patch
> author.
Thanks, will look.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL De
On Mon, Jul 1, 2013 at 3:43 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8273
> Logged by: David Leverton
> Email address: levert...@googlemail.com
> PostgreSQL version: Unsupported/Unknown
> Operating system: RHEL 5 x86_64
> Description:
The following bug has been logged on the website:
Bug reference: 8273
Logged by: David Leverton
Email address: levert...@googlemail.com
PostgreSQL version: Unsupported/Unknown
Operating system: RHEL 5 x86_64
Description:
The following test case causes a backend asser
