Re: Exposing the stats snapshot timestamp to SQL

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Matt Kelly <mkellycs(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Exposing the stats snapshot timestamp to SQL
Date: 2015-01-29 23:49:43
Message-ID: 54CAC717.6000703@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/28/15 11:18 PM, Matt Kelly wrote:
> In a previous thread Tom Lane said:
>
> (I'm also wondering if it'd make sense to expose the stats timestamp
> as a callable function, so that the case could be dealt with
> programmatically as well. But that's future-feature territory.)
>
> (http://www.postgresql.org/message-id/27251.1421684169@sss.pgh.pa.us)
>
> It seemed the appropriate scope for my first submission, and that feature has been on my wish list for a while, so I thought I'd grab it.

I've reviewed the patch (though haven't tested it myself) and it looks good. The only thing I'm not sure of is this:

+ /* Get the timestamp of the current statistics snapshot */
+ Datum
+ pg_stat_snapshot_timestamp(PG_FUNCTION_ARGS)
+ {
+ PG_RETURN_TIMESTAMPTZ(pgstat_fetch_global()->stats_timestamp);
+ }

Is the community OK with referencing stats_timestamp that way?
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Steele 2015-01-29 23:53:21 Re: pg_upgrade and rsync
Previous Message Jim Nasby 2015-01-29 23:44:07 Re: TABLESAMPLE patch