From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system |
Date: | 2013-02-17 05:46:54 |
Message-ID: | 20130217054654.GB6000@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tomas Vondra wrote:
> I've been thinking about this (actually I had a really weird dream about
> it this night) and I think it might work like this:
>
> (1) check the timestamp of the global file -> if it's too old, we need
> to send an inquiry or wait a bit longer
>
> (2) if it's new enough, we need to read it a look for that particular
> database - if it's not found, we have no info about it yet (this is
> the case handled by the dummy files)
>
> (3) if there's a database stat entry, we need to check the timestamp
> when it was written for the last time -> if it's too old, send an
> inquiry and wait a bit longer
>
> (4) well, we have a recent global file, it contains the database stat
> entry and it's fresh enough -> tadaaaaaa, we're done
Hmm, yes, I think this is what I was imagining. I had even considered
that the timestamp would be removed from the per-db file as you suggest
here.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Amit kapila | 2013-02-17 06:35:05 | Re: [PATCH] Add PQconninfoParseParams and PQconninfodefaultsMerge to libpq |
Previous Message | Shigeru Hanada | 2013-02-17 04:28:47 | Re: FDW for PostgreSQL |