| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Is it possible to keep track of SELECTs? |
| Date: | 2024-03-12 15:47:40 |
| Message-ID: | 9799ff799697aa400573647d5f0c6f39722819fb.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2024-03-12 at 16:34 +0100, Dominique Devienne wrote:
> PostgreSQL tables and indexes are ultimately files.
> And there are ways to map them to file names, I've seen in the past.
> So isn't it possible, provided the filesystem tracks last access time, to infer when a table was accessed the last time?
Sure, but that won't necessarily tell you when the table was last used.
It could be autovacuum or autoanalyze that last accessed your table.
Also, if the data happen to be in shared buffers, the file won't be read.
Using the PostgreSQL statistics is a much better method.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Avi Weinberg | 2024-03-12 15:57:48 | RE: [External] Simple way to simulate a bug in logical replication |
| Previous Message | Dominique Devienne | 2024-03-12 15:34:17 | Re: Is it possible to keep track of SELECTs? |