From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER SYSTEM SET typos and fix for temporary file name management |
Date: | 2014-01-22 00:02:39 |
Message-ID: | CAB7nPqTbnrr5BPO37ZyXOuNiG-ab+1U5V-YkS65tWGmA0uVS5A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 22, 2014 at 5:29 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> I agree with Michael that having pg_basebackup be aware of the ".temp"
> suffix is ugly; for instance if we were to fix it to ".tmp" in ALTER
> SYSTEM but forgot to change pg_basebackup, the check would be
> immediately broken. But on the other hand I'm not sure why it's such a
> problem for pg_basebackup that it needs to be checking in the first
> place -- how about we rip that out?
Coupled with the addition of a pgsql_tmp prefix to the temp
configuration file name would work, yes we could remove this check
part.
> Perhaps the temp file needs to be in pgsql_tmp? (Do we need to worry
> about cross-filesystem links if we do? I mean, do we support mounting
> pgsql_tmp separately?)
Using pgsql_tmp looks a bit weird as well, as this prefix is used only
for temporary files doing database-related operations, and ALTER
SYSTEM is not one. Doing that this would need a mention in the docs at
least:
http://www.postgresql.org/docs/devel/static/storage-file-layout.html
Thoughts?
Regards,
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2014-01-22 00:02:55 | Re: pg_upgrade & tablespaces |
Previous Message | Bruce Momjian | 2014-01-22 00:01:31 | Re: proposal: hide application_name from other users |