Re: Avoiding Tablespace path collision for primary and standby

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ashwin Agrawal <aagrawal(at)pivotal(dot)io>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, bruce(at)momjian(dot)us, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Avoiding Tablespace path collision for primary and standby
Date: 2018-06-20 20:30:42
Message-ID: 28797.1529526642@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ashwin Agrawal <aagrawal(at)pivotal(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robbie Harwood 2018-06-20 20:34:10 Re: libpq compression
Previous Message Tom Lane 2018-06-20 20:24:03 Re: ERROR: ORDER/GROUP BY expression not found in targetlist