Chris Travers wrote:
lec wrote:
Scott Marlowe wrote:
On Sun, 2004-08-08 at 19:43, lec wrote:
Hi,
I'm observing the following:
If I commit the following records 1,2,3,4,5,6,7,8,9,10 to the
database and the server hangs, I could lose records 5,6,7,8,9 but
record 10 is there. How
Tom Lane wrote:
I'm puzzled too. I don't suppose you have the postmaster log from when
it was trying to recover from the crash? Or even better, copies of the
WAL files?
I never knew where the log files are :(
---(end of broadcast)---
TIP 3: if
before the rest, and if that happened not to get
corrupted by the MB problem, we could see the result lec describes.
Of course this is all guesswork since we have no direct evidence to look
at, but it seems fairly plausible.
Anyway, if your CPU/RAM is failing, no DB technology can save you
Hi,
I'm observing the following:
If I commit the following records 1,2,3,4,5,6,7,8,9,10 to the database
and the server hangs, I could lose records 5,6,7,8,9 but record 10 is
there. How is this possible and do anyone know how Postgresql
physically writes the records?
Thanks,
thomas.
I always have to dump restore to make a database (which is in use for
a few months) efficient again. I have scheduled nightly vacuum analyze,
but only dump restore can make the database efficient again. Has
anyone experience this?
-lec
---(end of broadcast
After upgrading to 7.0.2, one of my queries ran much slower on 7.0.2:
7.0.2 took 17 minutes (After 'optimization' by SET ENABLE_SEQSCAN=OFF)
6.5.3 took 2 minutes
The following is the query/explain under 6.5.3:
super= select version();
version
Tom Lane wrote:
lec [EMAIL PROTECTED] writes:
Under 7.0.2, there are no Hash Join or Hash
So, then, what *does* it do? Without the explain for 7.0.2 it's
impossible to tell what's happening.
I'll re-install 7.0.2 later run the explain.
Are there any way to optimize this type
Tom Lane wrote:
lec [EMAIL PROTECTED] writes:
Under 7.0.2, there are no Hash Join or Hash
So, then, what *does* it do? Without the explain for 7.0.2 it's
impossible to tell what's happening.
The following is the query/explain under
