From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Zeugswetter Andreas SB" <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: Proposed WAL changes |
Date: | 2001-03-07 04:38:42 |
Message-ID: | EKEJJICOHDIEMGPNIFIJKEMBDMAA.Inoue@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Zeugswetter Andreas SB
>
> > >> Remove archdir from pg_control; it ought to be a GUC
> > >> parameter, not a special case (not that it's implemented
> > yet anyway).
> >
> > > Is archdir really a GUC parameter ?
> >
> > Why shouldn't it be? I see nothing wrong with changing it on-the-fly.
>
> Yes, I think this is a good change, like all others except XID
> assignment :-)
>
Could GUC parameters be changed permanently e.g. by SET command ?
For example,
1) start postmaster
2) set archdir to '....'
3) shutdown postmaster
Does PostgreSQL remember the archdir parameter ?
Regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-03-07 05:16:03 | Re: Proposed WAL changes |
Previous Message | Hiroshi Inoue | 2001-03-07 04:38:36 | RE: How to shoot yourself in the foot: kill -9 postmaster |