Re: Oid registry

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Oid registry
Date: 2012-09-25 15:21:56
Message-ID: 1348586360-sup-6928@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Hitoshi Harada's message of mar sep 25 02:11:14 -0300 2012:

> Of course you can
> look up type name conlusting SysCache and see if the type name is
> "hstore", but it's expensive to do it for every function invocation,
> so caching the hstore's oid in plv8 is the current workaround, which
> is not truly safe because the hstore's oid may change while caching.

Hm, couldn't you just register an invalidation callback with
CacheRegisterSyscacheCallback()?

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2012-09-25 15:27:06 Re: Re: [WIP] Performance Improvement by reducing WAL for Update Operation
Previous Message Brian Weaver 2012-09-25 15:10:59 Re: Patch: incorrect array offset in backend replication tar header