Re: pg_stat_*_columns?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joel Jacobson <joel(at)trustly(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat_*_columns?
Date: 2015-06-23 20:32:54
Message-ID: CA+Tgmoaf3SqTLfns3VXm15KUA7qhsRZgN6QHO5ir7rcRhYCMiw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 23, 2015 at 3:47 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2015-06-22 21:05:52 -0400, Robert Haas wrote:
>> Interesting idea. We could consider the set of stats files a database
>> unto itself and reserve a low-numbered OID for it. The obvious thing
>> to do is use the database's OID as the relfilenode, but then how do
>> you replace the stats file?
>
> The relmapper infrastructure should be able to take care of that.

How? I think it assumes that the number of mapped entries is pretty small.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2015-06-23 20:40:35 Re: proposal: row_to_array function
Previous Message Robert Haas 2015-06-23 20:28:18 Re: Should we back-patch SSL renegotiation fixes?