Not in a huge hurry (fixed right is better than fixed fast); just trying
to figure out where the fix is in terms of progress.
Koichi Suzuki wrote:
> Not yet. I'm rebuilding the test suit for better testing. If you're
> in a hurry, I can send you an update for test.
>
> --
> Koichi Suzuk
Has there been an update on this situation?
Koichi Suzuki wrote:
> I understand the situation. I'll upload the improved code ASAP.
>
> --
> Koichi Suzuki
>
>
>
> 2010/2/11 Karl Denninger :
>
>> Will this come through as a commit on the pgfoundry codebase? I've
>> subscribed looking f
Not yet. I'm rebuilding the test suit for better testing. If you're
in a hurry, I can send you an update for test.
--
Koichi Suzuki
2010/4/19 Karl Denninger :
> Has there been an update on this situation?
>
> Koichi Suzuki wrote:
>
> I understand the situation. I'll upload the impr
I understand the situation. I'll upload the improved code ASAP.
--
Koichi Suzuki
2010/2/11 Karl Denninger :
> Will this come through as a commit on the pgfoundry codebase? I've
> subscribed looking for it
>
> The last edit, if I read the release notes and tracebacks on the codeba
Will this come through as a commit on the pgfoundry codebase? I've
subscribed looking for it
The last edit, if I read the release notes and tracebacks on the
codebase correctly, goes back to the early part of 2009 - which strongly
implies that there are a **LOT** of people out there that coul
I found it's pg_compresslog problem (calculation of XNOOP record
length used in pg_decompresslog).I'm fixing the bug and will
upload the fix shortly.
Sorry for inconvenience.
--
Koichi Suzuki
2010/2/8 Karl Denninger :
> This may belong in a bug report, but I'll post it here f
Koichi-san,
seems, very similar problem.
Regards,
Oleg
On Sun, 7 Feb 2010, Karl Denninger wrote:
This may belong in a bug report, but I'll post it here first...
There appears to be a **SERIOUS** problem with using pg_compresslog and
pg_uncompresslog with Postgresql 8.4.2.
Here's my confi
This may belong in a bug report, but I'll post it here first...
There appears to be a **SERIOUS** problem with using pg_compresslog and
pg_uncompresslog with Postgresql 8.4.2.
Here's my configuration snippet:
full_page_writes = on # recover from partial page writes
wal_buffers
