From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marko Kreen <markokr(at)gmail(dot)com> |
Cc: | Postgres Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [9.2] Confusion over CacheRegisterSyscacheCallback |
Date: | 2012-03-06 21:27:11 |
Message-ID: | 20294.1331069231@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Marko Kreen <markokr(at)gmail(dot)com> writes:
> On Tue, Mar 06, 2012 at 11:10:38AM -0500, Tom Lane wrote:
>> Why would you need to know that? The reason the calculation function
>> is static is that there's no apparent need to expose that information
>> outside the syscache subsystem.
> Because I need to invalidate my own internal state that corresponds
> to particular system catalog row?
> In current case (plproxy) I need to invalidate libpq connections
> that are created from particular foreign server entry.
[ shrug... ] You could just flush 'em all, which is what most existing
inval callbacks do. Admittedly a libpq connection is a bit more
expensive than the average bit of invalidatable state, but how often
does pg_foreign_server get updated?
Or you could do like setrefs.c does, and assume you know how to
calculate the hash value for an OID-keyed cache.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2012-03-06 21:27:51 | Re: foreign key locks, 2nd attempt |
Previous Message | Dimitri Fontaine | 2012-03-06 21:26:15 | Re: How to know a table has been modified? |