On Mon, 2012-01-23 at 01:08 +, a...@arencambre.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6406
> Logged by: Aren Cambre
> Email address: a...@arencambre.com
> PostgreSQL version: 9.1.2
> Operating system: Windows 7 x64
> Description:
Hi all,
trying to create a table with a column xmin I get the
following error message:
test=> create table lx (xmin int);
ERROR: column name "xmin" conflicts with a system
column name
Instead I get a different (and less understandable) error
message if I try to add a column named xmin to an
exi
Am 22.01.12 14:22, schrieb Giuseppe Sucameli:
> Hi all,
>
> trying to create a table with a column xmin I get the
> following error message:
>
> test=> create table lx (xmin int);
> ERROR: column name "xmin" conflicts with a system
> column name
>
> Instead I get a different (and less understan
On Mon, Jan 23, 2012 at 11:25, Marc Balmer wrote:
> Am 22.01.12 14:22, schrieb Giuseppe Sucameli:
> > test=> create table lx (xmin int);
> > ERROR: column name "xmin" conflicts with a system
> > column name
> >
> > test=> create table lx (i int);
> > CREATE TABLE
> > test=> alter table lx add xm
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 (and sometimes completely wrong) answers
this is 9.1.2 on Deb
Hello,
We upgraded to postgres 9.1.2 two weeks ago, and we are also experiencing
an issue that seems very similar to the one reported as bug 6200. We see
approximately 2 dozen alloc errors per day across 3 slaves, and we are
getting one segfault approximately every 3 days. We did not experience
t
Running Postgres 9.1.2.
I've attached a backtrace. Looking at the backtrace it looks like
ExecGetResultType() gets called with a NULL planstate and causes the
segmentation fault:
https://github.com/postgres/postgres/blob/master/src/backend/executor/execUtils.c#L470
Following the stack I see that
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.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your s
