Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Christophe Pettus <christophe(dot)pettus(at)pgexperts(dot)com>, Postgres-Bugs <pgsql-bugs(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?
Date: 2018-01-13 02:42:49
Message-ID: CA+TgmoZ+jgzR9XETuopFcBJij=3nO17t3YctLS9VaM+qm2hfUA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Fri, Jan 12, 2018 at 5:06 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> OTOH, it seems quite likely that we'll add more transaction-lifetime
> shared data (e.g. combocid), so building per-xact infrastructure
> actually seems like a good idea.

Sure, but there's no urgency about it. Particularly if the first cut
at this is implemented using dshash, moving the dshash to a different
DSA with a different lifespan later should be easy.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-01-14 10:33:22 BUG #15009: connection to server
Previous Message Andres Freund 2018-01-12 22:06:12 Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2018-01-13 03:39:09 Re: Possible performance regression with pg_dump of a large number of relations
Previous Message Tomas Vondra 2018-01-13 02:25:55 Re: [PROPOSAL] Shared Ispell dictionaries