Re: Avoiding Tablespace path collision for primary and standby - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Avoiding Tablespace path collision for primary and standby
Date
Msg-id 28797.1529526642@sss.pgh.pa.us
Whole thread Raw
In response to Re: Avoiding Tablespace path collision for primary and standby  (Ashwin Agrawal <aagrawal@pivotal.io>)
Responses Re: Avoiding Tablespace path collision for primary and standby
List pgsql-hackers
Ashwin Agrawal <aagrawal@pivotal.io> writes:
> Okay just bouncing another approach, how about generating UUID for a
> postgres instance during initdb and pg_basebackup ?

There's no uuid generation code in core postgres, for excellent reasons
(lack of portability and lack of failure modes are the main objections).
This is not different in any meaningful way from the proposal to use
timestamps, except for being more complicated.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ERROR: ORDER/GROUP BY expression not found in targetlist
Next
From: Robbie Harwood
Date:
Subject: Re: libpq compression