Hi,
After dropping some tables in my PG 8.3 DB I tried to execute 'vacuum
full' command and got the error:
ERROR: invalid memory alloc request size 4294967280
SQL state: XX000
Up to now the error has not reproduced once again.
select version();
"PostgreSQL 8.3.0, compiled by Vi
: Zubkovsky, Sergey
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] ERROR: tuple concurrently updated
"Zubkovsky, Sergey" <[EMAIL PROTECTED]> writes:
> create table t1 ( id int );
> create temp view v1 as select * from t1;
> C1: begin; drop view v1;
> C2: drop table t1;
It was Kaspersky antivirus with its on-fly "*:KAVICHS" NTFS-streams.
Thanks.
-Original Message-
From: Dave Page [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 28, 2007 11:36 AM
To: Magnus Hagander
Cc: Zubkovsky, Sergey; pgsql-bugs@postgresql.org
Subject: Re: [BUGS] "Pe
Hello.
Testing of the concurrent access to database objects leaded to the following
error:
ERROR: tuple concurrently updated
SQL state: XX000
According to the "PostgreSQL Error Codes" table in the documentation, "XX000"
is the PostgreSQL internal error code.
How to reproduce
Hello.
In spite of the fact that as it was outlined in the "change log" to PostgreSQL
8.2.2, the bug of the periodical "permission denied" error occurrence was fixed:
"Fix bogus "permission denied" failures occurring on Windows due to attempts
to fsync already-deleted files (Magnus, Tom
select version();
"PostgreSQL 8.2.1 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC)
3.4.2 (mingw-special)"
pg_log:
2007-01-12 16:41:23 STATEMENT: EXPLAIN COPY "MsgRoot" TO 'C:/Program
Files/PostgreSQL/8.2/data/MsgRoot.txt'
2007-01-12 17:16:04 LOG: checkpoints are occurring too frequen
Hi,
SELECT to_char(
'2006-01-01'::timestamp, 'IYYY-MM-DD' ) AS strange,
to_char( '2006-01-02'::timestamp, 'IYYY-MM-DD' ),
to_char( '2006-01-01'::timestamp, '-MM-DD' );
does produce unexpected result for column ‘strange’:
strange
| to_char | to_char
-
