From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: odd problem ! |
Date: | 2005-03-23 00:07:23 |
Message-ID: | 29977.1111536443@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
>> This isn't a problem in normal use of course, but it'd be a serious
>> issue for someone engaging in WAL-shipping, if their backup postmaster
>> were living at a different absolute path. We probably need to think
> right, this is normal situation if you backup to the same server.
> Not sure how it's usefull, but still
>> about whether we can make CREATE DATABASE log only relative paths.
> any problem ?
I've committed a fix --- please check that it solves your problem.
(I have to leave for a few hours so I can't check it myself right away.)
>> Log-shipping CREATE TABLESPACE commands is even more interesting :-(.
>> Not sure how to deal with that.
> in general case it's impossible.
Yeah :-( ... needs more thought.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-03-23 00:37:07 | Re: Prevent conflicting SET options from being set |
Previous Message | Oleg Bartunov | 2005-03-22 23:22:41 | Re: odd problem ! |