PostgreSQL 8.0.2beta1 (REL8_0_STABLE updated this morning)
FreeBSD 4.11-STABLE
gcc 2.95.4
While investigating somebody's question I ran the following query,
which caused the backend to segfault:
SELECT * FROM foo WHERE first_date = now() AND last_date = now();
I have to run so I can't put
Michael Fuhr [EMAIL PROTECTED] writes:
While investigating somebody's question I ran the following query,
which caused the backend to segfault:
SELECT * FROM foo WHERE first_date = now() AND last_date = now();
I have to run so I can't put together a test case right now, but
here's the stack
On Fri, Apr 01, 2005 at 02:46:10PM -0500, Tom Lane wrote:
Mumble ... that patch I put in last week doesn't work at all, does it?
Back to the drawing board.
I don't get the crash any more with the change you applied a little
while ago. Here's a test case that was crashing:
CREATE TABLE foo (
Hi folks.
There's a problem in the console detach code for pg_autovacuum.
setsid() is NOT sufficient. Specifically, you must disassociate the
control terminal (standard in, out and error) for it to be complete.
This causes any attempt to execute pg_autovacuum from the cron to hang the
cron
Hello all!!
I'm in a trouble restoring a database.
System:
PostgreSQL 8.0
Windows 2000 Professional SP4
when I do pg_dump to backup mydb:
C:\Archivos de programa\PostgreSQL\8.0\binpg_dump -U juan --format=c
mydb back2
Password:
pg_dump: [custom archiver] WARNING: ftell mismatch with expected
Anyone else notice breakage from 8.0.0 to 8.0.1 using msvc(6)? Was just
about to update my client libraries and I got an unresolved external
symbol SHGetFolderPath in fe-connect.c, wasn't 8.0.0 using
SHGetSpecialFolderPath?
---(end of
Why would you run pg_autovacuum from cron?
Karl Denninger wrote:
Hi folks.
There's a problem in the console detach code for pg_autovacuum.
setsid() is NOT sufficient. Specifically, you must disassociate the
control terminal (standard in, out and error) for it to be complete.
This causes any
I have a process which does backups by mounting a disk into a RAID array,
allowing it to sync, then it must stop the database before detaching it so
as to insure that the DBMS is consistent on the backup disk.
Once detached, Postgres must be restarted, of course..
This process is MUCH faster
