Tom Lane wrote:
>
> "Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> > So, it's better to leave archdir in pg_control now - if we'll
> > decide that GUC is better place then we'll just ignore archdir
> > in pg_control. But if it will be better to have it in pg_control
> > then we'll not be able to add it there.
>
> But what possible reason is there for keeping it in pg_control?
> AFAICS that would just mean that we'd need special code for setting it,
> instead of making use of all of Peter's hard work on GUC.
>
I don't think it's appropriate to edit archdir by hand.
Regards,
Hiroshi Inoue
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
- Re: [HACKERS] Proposed WAL changes Hiroshi Inoue
- Re: [HACKERS] Proposed WAL changes Tom Lane
- Re: [HACKERS] Proposed WAL changes Peter Eisentraut
- AW: [HACKERS] Proposed WAL changes Zeugswetter Andreas SB
- Re: AW: [HACKERS] Proposed WAL changes Hiroshi Inoue
- Re: AW: [HACKERS] Proposed WAL changes Vadim Mikheev
- Re: AW: [HACKERS] Proposed WAL changes Bruce Momjian
- Re: AW: [HACKERS] Proposed WAL changes Tom Lane
- RE: AW: [HACKERS] Proposed WAL changes Mikheev, Vadim
- Re: AW: [HACKERS] Proposed WAL changes Tom Lane
- Re: AW: [HACKERS] Proposed WAL changes Hiroshi Inoue
- Re: AW: [HACKERS] Proposed WAL changes Tom Lane
- Re: AW: [HACKERS] Proposed WAL cha... Hiroshi Inoue
- Re: AW: [HACKERS] Proposed WA... Tom Lane
- Re: AW: [HACKERS] Propose... Hiroshi Inoue