Bruce Momjian writes:
> Should we start planning for an 8.1.1?
Yeah, it's getting to be that time.
regards, tom lane
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choos
Tom Lane wrote:
> Kari Lavikka <[EMAIL PROTECTED]> writes:
> > Some backtraces (update queries are included in the bt):
> >http://tuner.bdb.fi/pg_crashing.txt
> >http://tuner.bdb.fi/pg_crashing2.txt
> >http://tuner.bdb.fi/pg_crashing3.txt
>
> This looks to be the toast-vs-index bug alr
Kari Lavikka <[EMAIL PROTECTED]> writes:
> Some backtraces (update queries are included in the bt):
>http://tuner.bdb.fi/pg_crashing.txt
>http://tuner.bdb.fi/pg_crashing2.txt
>http://tuner.bdb.fi/pg_crashing3.txt
This looks to be the toast-vs-index bug already identified.
Patch is here
Hi!
I just upgraded pg 8.0.3 to 8.1 (dump and reload) and outcome was a
corrupted database. pg 8.1 seemed to fly but backends were crashing
:-/
Hardware is Sun v40z with 64bit Debian Sarge, Linux 2.6.13.2. Size of
database is somewhere around 500M rows and it's loaded by a website with a
lo
my previous post just vanished...
Hi!
I just upgraded pg 8.0.3 to 8.1 (dump and reload) and outcome was a
corrupted database. pg 8.1 seemed to fly but backends were crashing :-/
While tailing the log file I noticed a couple of:
ERROR: invalid memory alloc request size 1101389186
Hardware
