On Thu, 24 Mar 2005, Tom Lane wrote:
> Gavin Sherry <[EMAIL PROTECTED]> writes:
> >> The hard part is CREATE TABLESPACE, and the reason it's hard is that
> >> someone might possibly want the tablespace to be located at a different
> >> place on the recipient machine than it is on the master. I do
Gavin Sherry <[EMAIL PROTECTED]> writes:
>> The hard part is CREATE TABLESPACE, and the reason it's hard is that
>> someone might possibly want the tablespace to be located at a different
>> place on the recipient machine than it is on the master. I do not see a
>> reasonable way to support that a
On Wed, 23 Mar 2005, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > On Tue, 2005-03-22 at 21:42 -0500, Bruce Momjian wrote:
> >> Is this a TODO?
>
> > Yes, it is.
>
> > In my experience, most people create only a single Database, then define
> > their Tablespaces (or change them rar
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Tue, 2005-03-22 at 21:42 -0500, Bruce Momjian wrote:
>> Is this a TODO?
> Yes, it is.
> In my experience, most people create only a single Database, then define
> their Tablespaces (or change them rarely, if ever). So I've always
> regarded CREATE DATA
On Wed, 2005-03-23 at 13:07 +, Simon Riggs wrote:
> On Tue, 2005-03-22 at 19:07 -0500, Tom Lane wrote:
> > Oleg Bartunov 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
On Tue, 2005-03-22 at 19:07 -0500, Tom Lane wrote:
> Oleg Bartunov 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
I checked stable branch. no problem now.
Oleg
On Tue, 22 Mar 2005, Tom Lane wrote:
Oleg Bartunov 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
On Tue, 2005-03-22 at 21:42 -0500, Bruce Momjian wrote:
> Tom Lane wrote:
> > Oleg Bartunov 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 pa
Tom Lane wrote:
> Oleg Bartunov 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 situat
Oleg Bartunov 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 sam
On Tue, 22 Mar 2005, Tom Lane wrote:
Oleg Bartunov writes:
What PG version is this exactly?
REL8_0_STABLE, I believe. I posted another problem, now "cut and pasted".
I've been able to duplicate this here. What is happening is that the
damage to ./t1 is being done when you start the postmaster in
Oleg Bartunov writes:
>> What PG version is this exactly?
> REL8_0_STABLE, I believe. I posted another problem, now "cut and pasted".
I've been able to duplicate this here. What is happening is that the
damage to ./t1 is being done when you start the postmaster in ./t2.
It looks to me like the
On Tue, 22 Mar 2005, Tom Lane wrote:
template1 | postgres | KOI8
test | postgres | KOI8
(3 rows)
11.
[EMAIL PROTECTED]:~/test$ psql test
FATAL: database "test" does not exist
psql: FATAL: database "test" does not exist
What PG version is this exactly? I suppose that you're seeing one o
Oleg Bartunov writes:
> below is the problem I just bitten when play with toy db. I did:
> 1.initdb -D ./t1
> 2. pg_ctl -D ./t1 start
> 3. createdb test
> 4. psql test -c "create table a (f integer);"
> 5. run script which populates table a in background
> perl bgupdate.pl &
> 6. cp -a ./t1 .
OK, here is more cleaner cut and paste from my notebook:
[EMAIL PROTECTED]:~/test$ initdb -D ./t1
[EMAIL PROTECTED]:~/test$ pg_ctl -D ./t1 start
postmaster starting
[EMAIL PROTECTED]:~/test$ LOG: database system was shut down at 2005-03-23
01:09:34 MSK
LOG: checkpoint record is at 0/A2C844
LOG:
15 matches
Mail list logo
