Re: pg_ls_tmpdir()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
Cc: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Christoph Berg <myon(at)debian(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_ls_tmpdir()
Date: 2018-10-02 16:46:42
Message-ID: 26978.1538498802@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Bossart, Nathan" <bossartn(at)amazon(dot)com> writes:
> On 10/2/18, 7:22 AM, "Andrew Dunstan" <andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
>> See the bottom of src/backend/catalog/system_views.sql starting around
>> line 1010.

> AFAICT the cleanest way to do this in system_views.sql is to hard-code
> the pg_default tablespace OID in the DEFAULT expression. So, it might
> be best to use the two function approach if we want pg_ls_tmpdir() to
> default to the pg_default tablespace.

That would be pretty bletcherous, so +1 for just making two C functions.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2018-10-02 16:58:13 Re: transction_timestamp() inside of procedures
Previous Message Tom Lane 2018-10-02 16:45:04 Re: has_column_privilege behavior (was Re: Assert failed in snprintf.c)