Hi,
At Mon, 15 May 2017 14:35:20 +0900, Michael Paquier
wrote in
> On Thu, May 11, 2017 at 1:09 PM, Kyotaro HORIGUCHI
> wrote:
> > If we can accept multiple server
On Thu, May 11, 2017 at 1:09 PM, Kyotaro HORIGUCHI
wrote:
> If we can accept multiple server versions share a tablespace
> directory, pg_basebackup also can allow that situation. The
> attached patch does that. Similary to the server code, it
> correctly fails if
Hello,
At Fri, 5 May 2017 21:42:47 +1000, Neha Khatri wrote in
> As Kyotaro san pointed out, the commit 22817041 started allowing creation
> of multiple "tablespace version directories" in same location.
As Kyotaro san pointed out, the commit 22817041 started allowing creation
of multiple "tablespace version directories" in same location. However the
original purpose of that commit was to allow that just for the upgrade
purpose. So couple of points:
- The commit violated the requirement of
I don't mean that this is the only or best way to go.
I apologize for the possible lack of explanation.
At Thu, 06 Apr 2017 12:03:51 -0400, Tom Lane wrote in
<21084.1491494...@sss.pgh.pa.us>
> Kyotaro HORIGUCHI writes:
> > I noticed by the
Kyotaro HORIGUCHI writes:
> I noticed by the following report, PostgreSQL can share the same
> directory as tablespaces of two servers with different
> pg-versions.
> https://www.postgresql.org/message-id/2008148.rxBNyNRHPZ@peanuts2
> 8.4 checked that the
Hello,
I noticed by the following report, PostgreSQL can share the same
directory as tablespaces of two servers with different
pg-versions.
https://www.postgresql.org/message-id/2008148.rxBNyNRHPZ@peanuts2
8.4 checked that the tablespace location is empty, but from 9.0,
the check is replaced