| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Matteo Sgalaberni <sgala(at)sgala(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: corrupted table postgresql 8.3 |
| Date: | 2012-03-07 18:01:45 |
| Message-ID: | CAHyXU0wx0PzXC9SsBC_BhPD1ekJh=M1MGaaYtfK-zzANoci3-A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Mar 6, 2012 at 6:34 PM, Matteo Sgalaberni <sgala(at)sgala(dot)com> wrote:
> ----- Original Message -----
>> On 6.3.2012 21:24, Matteo Sgalaberni wrote:
>> > Hi people!
>> >
>> > I have a pg 8.3. Today I issued in a database that comand:
>>
>> Which minor version? The last one in this branch is 8.3.18 and if
>> you're
>> running an old one, there might be an important bugfix ...
>
> 8.3.0, I read quickly all releases notes of 8.3.x and I didn't saw any fix that could be directly related to what is happened to me...there are issues related to ALTER TABLE but with other options like PRIMARY KEY or other parameters.
> Are there fixes that could be related to what's happened to me?
hm:
* Also, a VACUUM FULL that failed partway through vacuuming a system
catalog could result in cache corruption in concurrent database
sessions.
* Fix btree index corruption from insertions concurrent with vacuuming
(Tom Lane)
* These bugs could result in index corruption after reindexing a
system catalog. They are not believed to affect user indexes.
I mostly agree, but it's possible you got hit by a fixed bug.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matteo Sgalaberni | 2012-03-07 18:22:43 | Re: corrupted table postgresql 8.3 |
| Previous Message | Andrey Chursin | 2012-03-07 17:59:15 | Re: Full text search ranking: ordering using index and proximiti ranking with OR queries |