Hi,
Richard Huxton wrote:
Not a hacker myself, but I can tell you that the first question you'll
be asked is can you produce a test case? If you can generate the
problem from a test table+generated data that will let people figure out
the problem for you.
Unfortunately, I have not been able
Hi,
Simon Riggs wrote:
On Tue, 2009-06-09 at 13:40 +0200, Floris Bos / Maxnet wrote:
fsync = off
That's a bad plan if you care about your database.
I am aware of the risk of dataloss in case of power failure, etc.
However fsync=on is simply too slow for my purpose, and it concerns data
Hi,
Josh Berkus wrote:
It doesn't. But what I don't trust, and the *first* place I'd look for
problems, is whether the OS flushes *all* dirty buffers to disk in the
event the application gets killed.
That's why I want more information on Floris' case. Was 8.4 killed or
shut down with -m
Hi,
I pgdump'ed a 8.3.7 database and loaded the dump to a different server
running PostgreSQL 8.4 beta 2 (compiled from source) under Opensolaris.
One of the tables has about 6 million records, and a Btree index that
spans 3 columns.
I am having the problem that some queries are unable to
