Re: Why copy_relation_data only use wal whenWALarchivingis enabled - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Why copy_relation_data only use wal whenWALarchivingis enabled
Date
Msg-id 23216.1192718395@sss.pgh.pa.us
Whole thread Raw
In response to Re: Why copy_relation_data only use wal whenWALarchivingis enabled  ("Florian G. Pflug" <fgp@phlo.org>)
Responses Re: Why copy_relation_data only use wal whenWALarchivingis enabled
List pgsql-hackers
"Florian G. Pflug" <fgp@phlo.org> writes:
> What is the argument against making relfilenodes globally unique by adding the 
> xid and epoch of the creating transaction to the filename?

1. Zero chance of ever backpatching.  (I know I said I wasn't excited  about that, but it's still a strike against a
proposedfix.)
 

2. Adds new fields to RelFileNode, which will be a major code change,  and possibly a noticeable performance hit
(biggerhashtable keys).
 

3. Adds new columns to pg_class, which is a real PITA ...

4. Breaks oid2name and all similar code that knows about relfilenode.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Why copy_relation_data only use wal whenWALarchivingis enabled
Next
From: Tom Lane
Date:
Subject: Re: max_prepared_transactions default ... why 5?