and this time the patch is attached
Andrew Dunstan wrote:
Tom Lane wrote:
What I think we'd need to have a complete solution is
convert(text, name) returns bytea
-- convert from DB encoding to arbitrary encoding
convert(bytea, name, name) returns bytea
-- convert between any two
Tom Lane wrote:
What I think we'd need to have a complete solution is
convert(text, name) returns bytea
-- convert from DB encoding to arbitrary encoding
convert(bytea, name, name) returns bytea
-- convert between any two encodings
convert(bytea, name) returns text
--
Forgot to include this in the patch ...
I'm still unhappy about too much complexity for the VACUUM FULL case,
but some other issues have gone away.
regards, tom lane
$PostgreSQL$
Heap Only Tuples (HOT)
Introduction
The Heap Only
Hi All,
This patch is an add-on patch the version 15 posted earlier and
should be applied on top of version 15. The following review items
has been fixed:
- Fix the pruning code to prune all tuples upto and including the
latest DEAD tuple in the chain.
- Removed the heap tuple freezing changes b
Tom Lane wrote:
> Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
>> yeah testing that patch now (seems to apply just fine on -HEAD) but it
>> seems that there is something strange going on because I just got:
>
> ! ERROR: could not read block 2 of relation 1663/16384/2606: read only 0 of
> 819
Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
> yeah testing that patch now (seems to apply just fine on -HEAD) but it
> seems that there is something strange going on because I just got:
! ERROR: could not read block 2 of relation 1663/16384/2606: read only 0 of
8192 bytes
Is that repeatabl
Tom Lane wrote:
> Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
>> hmm i wonder if that could be related to:
>> http://archives.postgresql.org/pgsql-hackers/2007-01/msg00377.php
>
> I had forgotten that thread, but it sure does look related doesn't it?
> Do you want to try Steve's proposed patc
