| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | XXXXXX XXXXXXX <novikov(at)webclub(dot)ru> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] VACUUM problem |
| Date: | 1999-02-02 12:38:51 |
| Message-ID: | Pine.BSF.4.05.9902020837420.11157-100000@thelab.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2 Feb 1999, XXXXXX XXXXXXX wrote:
> Hello.
>
> Recently some users started to complain about:
> Warning: PostgresSQL query failed: FATAL 1: btree: lost page in the chain of duplicates
>
> I noticed that VACUUM removes this problem, but no making
> VACUUM I've got:
> NOTICE: BlowawayRelationBuffers(confread, 45): block 154 is referenced (private 0, last 0,
> global 1)
> FATAL 1: VACUUM (vc_rpfheap): BlowawayRelationBuffers returned -2
>
> What it can be? I'm using 6.3.2
A relatively old version of PostgreSQL...upgrade to v6.4.2, as I
believe this was fixed several months ago, in v6.4...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 1999-02-02 13:08:05 | Re: [HACKERS] trouble with rules |
| Previous Message | novikov | 1999-02-02 12:15:20 | VACUUM problem |