On Tue, Jan 24, 2012 at 14:41, Giuseppe Sucameli wrote:
> > I would try to cook up a patch but I have no skills :-(
>
> I'm going to write a patch to fix this problem.
I managed to put something together and have posted it on hackers.
On 01/23/2012 08:40 PM, Stefan Kaltenbrunner wrote:
> We are using the raw decryption features of contrib/pgcrypto here to
> decode certain AES128 encrypted data. However depending on the data to
> decode and what statements have been executed in the same session before
> we are seeing different (a
Phil Sorber writes:
> On Tue, Jan 24, 2012 at 12:43 AM, Tom Lane wrote:
>> How about a test case?
> We are having trouble coming up with a test case that can reliably
> reproduce this.
The stack traces run through the EvalPlanQual machinery, which is only
going to be entered when attempting to
On Tue, Jan 24, 2012 at 12:43 AM, Tom Lane wrote:
> Phil Sorber writes:
>> I've attached a backtrace.
>
> How about a test case? I have no faith in the proposed patch without
> some evidence of what it's supposed to fix.
We are having trouble coming up with a test case that can reliably
reprodu
Hi Marc,
On Mon, Jan 23, 2012 at 3:04 PM, Vik Reykja wrote:
> On Mon, Jan 23, 2012 at 11:25, Marc Balmer wrote:
>>
>> Am 22.01.12 14:22, schrieb Giuseppe Sucameli:
>> > test=> create table lx (i int);
>> > CREATE TABLE
>> > test=> alter table lx add xmin int;
>> > ERROR: column "xmin" of relati
Hello!
I'm sorry that I could not answer at once.
Meanwhile I investigated the matter of my problem, learned about SSI
(mostly at http://wiki.postgresql.org/wiki/Serializable) and
realized that we wouldn't need "serializable" transaction isolation
level anymore (thanks to SSI). So I just turned i
