Skip site navigation (1) Skip section navigation (2)

Re: Possible savepoint bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paesold <mpaesold(at)gmx(dot)at>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Possible savepoint bug
Date: 2005-12-27 22:22:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
I wrote:
> Michael Paesold <mpaesold(at)gmx(dot)at> writes:
>> I am seeing a similar unique index bug here...
>> This is PostgreSQL 8.1.1 on RHEL 3, Intel Xeon (i686).

> It looks like the problem is that index entries are being inserted out
> of order.

After further investigation, it seems that the original sort order of
the index was not C-locale, but something else --- I can reproduce the
current index ordering except for a small number of new-ish tuples if
I sort the data in en_US.

We go out of our way to prevent the backend's locale from changing after
initdb.  Did you do something to override that?

Another theory is that this is a manifestation of the known problem with
plperl sometimes changing the backend's locale setting.  Is it possible
that the index was created in a session that had previously run some
plperl functions?

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Hannu KrosingDate: 2005-12-27 22:41:57
Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
Previous:From: Pavel StehuleDate: 2005-12-27 21:44:25
Subject: Re: Oracle PL/SQL Anonymous block equivalent in postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group