pg.ddx.io pgsql-committers@postgresql.org mailing list archive
help / color / mirror / Atom feedpgsql: Cache by-reference missing values in a long lived context
15+ messages / 3 participants
[nested] [flat]
Commits from this thread:
2023-08-27 dd9779141e f06e1711d2 Silence compiler warning in release 11 and 12 branches
* pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-22 19:17 Andrew Dunstan <andrew@dunslane.net>
0 siblings, 0 replies; 15+ messages in thread
From: Andrew Dunstan @ 2023-08-22 19:17 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Cache by-reference missing values in a long lived context
Attribute missing values might be needed past the lifetime of the tuple
descriptors from which they are extracted. To avoid possibly using
pointers for by-reference values which might thus be left dangling, we
cache a datumCopy'd version of the datum in the TopMemoryContext. Since
we first search for the value this only needs to be done once per
session for any such value.
Original complaint from Tom Lane, idea for mitigation by Andrew Dunstan,
tweaked by Tom Lane.
Backpatch to version 11 where missing values were introduced.
Discussion: https://postgr.es/m/1306569.1687978174@sss.pgh.pa.us
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/a68458108512890d03da39f0132b829ddd5a69ab
Modified Files
--------------
src/backend/access/common/heaptuple.c | 90 ++++++++++++++++++++++++++++++++++-
src/tools/pgindent/typedefs.list | 1 +
2 files changed, 90 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 15+ messages in thread
* pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-22 19:17 Andrew Dunstan <andrew@dunslane.net>
0 siblings, 0 replies; 15+ messages in thread
From: Andrew Dunstan @ 2023-08-22 19:17 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Cache by-reference missing values in a long lived context
Attribute missing values might be needed past the lifetime of the tuple
descriptors from which they are extracted. To avoid possibly using
pointers for by-reference values which might thus be left dangling, we
cache a datumCopy'd version of the datum in the TopMemoryContext. Since
we first search for the value this only needs to be done once per
session for any such value.
Original complaint from Tom Lane, idea for mitigation by Andrew Dunstan,
tweaked by Tom Lane.
Backpatch to version 11 where missing values were introduced.
Discussion: https://postgr.es/m/1306569.1687978174@sss.pgh.pa.us
Branch
------
REL_12_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/01993ac748fda69495912205440a767edef0e039
Modified Files
--------------
src/backend/access/common/heaptuple.c | 91 ++++++++++++++++++++++++++++++++++-
src/tools/pgindent/typedefs.list | 1 +
2 files changed, 91 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 15+ messages in thread
* pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-22 19:17 Andrew Dunstan <andrew@dunslane.net>
0 siblings, 0 replies; 15+ messages in thread
From: Andrew Dunstan @ 2023-08-22 19:17 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Cache by-reference missing values in a long lived context
Attribute missing values might be needed past the lifetime of the tuple
descriptors from which they are extracted. To avoid possibly using
pointers for by-reference values which might thus be left dangling, we
cache a datumCopy'd version of the datum in the TopMemoryContext. Since
we first search for the value this only needs to be done once per
session for any such value.
Original complaint from Tom Lane, idea for mitigation by Andrew Dunstan,
tweaked by Tom Lane.
Backpatch to version 11 where missing values were introduced.
Discussion: https://postgr.es/m/1306569.1687978174@sss.pgh.pa.us
Branch
------
REL_13_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/1bb619d4d6285c23f16da61fb3a17ef59b14b0c7
Modified Files
--------------
src/backend/access/common/heaptuple.c | 90 ++++++++++++++++++++++++++++++++++-
src/tools/pgindent/typedefs.list | 1 +
2 files changed, 90 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 15+ messages in thread
* pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-22 19:17 Andrew Dunstan <andrew@dunslane.net>
0 siblings, 0 replies; 15+ messages in thread
From: Andrew Dunstan @ 2023-08-22 19:17 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Cache by-reference missing values in a long lived context
Attribute missing values might be needed past the lifetime of the tuple
descriptors from which they are extracted. To avoid possibly using
pointers for by-reference values which might thus be left dangling, we
cache a datumCopy'd version of the datum in the TopMemoryContext. Since
we first search for the value this only needs to be done once per
session for any such value.
Original complaint from Tom Lane, idea for mitigation by Andrew Dunstan,
tweaked by Tom Lane.
Backpatch to version 11 where missing values were introduced.
Discussion: https://postgr.es/m/1306569.1687978174@sss.pgh.pa.us
Branch
------
REL_15_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/75f323aa1c1ec88f9781cb6d9307e42b820b26f0
Modified Files
--------------
src/backend/access/common/heaptuple.c | 90 ++++++++++++++++++++++++++++++++++-
src/tools/pgindent/typedefs.list | 1 +
2 files changed, 90 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 15+ messages in thread
* pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-22 19:17 Andrew Dunstan <andrew@dunslane.net>
0 siblings, 0 replies; 15+ messages in thread
From: Andrew Dunstan @ 2023-08-22 19:17 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Cache by-reference missing values in a long lived context
Attribute missing values might be needed past the lifetime of the tuple
descriptors from which they are extracted. To avoid possibly using
pointers for by-reference values which might thus be left dangling, we
cache a datumCopy'd version of the datum in the TopMemoryContext. Since
we first search for the value this only needs to be done once per
session for any such value.
Original complaint from Tom Lane, idea for mitigation by Andrew Dunstan,
tweaked by Tom Lane.
Backpatch to version 11 where missing values were introduced.
Discussion: https://postgr.es/m/1306569.1687978174@sss.pgh.pa.us
Branch
------
REL_14_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/7f4515a58ebd0ae967638b0a27c730cbd49b3455
Modified Files
--------------
src/backend/access/common/heaptuple.c | 90 ++++++++++++++++++++++++++++++++++-
src/tools/pgindent/typedefs.list | 1 +
2 files changed, 90 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 15+ messages in thread
* pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-22 19:18 Andrew Dunstan <andrew@dunslane.net>
0 siblings, 0 replies; 15+ messages in thread
From: Andrew Dunstan @ 2023-08-22 19:18 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Cache by-reference missing values in a long lived context
Attribute missing values might be needed past the lifetime of the tuple
descriptors from which they are extracted. To avoid possibly using
pointers for by-reference values which might thus be left dangling, we
cache a datumCopy'd version of the datum in the TopMemoryContext. Since
we first search for the value this only needs to be done once per
session for any such value.
Original complaint from Tom Lane, idea for mitigation by Andrew Dunstan,
tweaked by Tom Lane.
Backpatch to version 11 where missing values were introduced.
Discussion: https://postgr.es/m/1306569.1687978174@sss.pgh.pa.us
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/f938acd68b08704a086b5f41eaf1989026d6f013
Modified Files
--------------
src/backend/access/common/heaptuple.c | 90 ++++++++++++++++++++++++++++++++++-
src/tools/pgindent/typedefs.list | 1 +
2 files changed, 90 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 15+ messages in thread
* pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-23 21:22 Andrew Dunstan <andrew@dunslane.net>
0 siblings, 1 reply; 15+ messages in thread
From: Andrew Dunstan @ 2023-08-23 21:22 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Cache by-reference missing values in a long lived context
Attribute missing values might be needed past the lifetime of the tuple
descriptors from which they are extracted. To avoid possibly using
pointers for by-reference values which might thus be left dangling, we
cache a datumCopy'd version of the datum in the TopMemoryContext. Since
we first search for the value this only needs to be done once per
session for any such value.
Original complaint from Tom Lane, idea for mitigation by Andrew Dunstan,
tweaked by Tom Lane.
Backpatch to version 11 where missing values were introduced.
Discussion: https://postgr.es/m/1306569.1687978174@sss.pgh.pa.us
Branch
------
REL_11_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/2d13dab048a7e0777875529620f81d32ce57dfd8
Modified Files
--------------
src/backend/access/common/heaptuple.c | 91 ++++++++++++++++++++++++++++++++++-
src/tools/pgindent/typedefs.list | 1 +
2 files changed, 91 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-24 15:27 Tom Lane <tgl@sss.pgh.pa.us>
parent: Andrew Dunstan <andrew@dunslane.net>
0 siblings, 1 reply; 15+ messages in thread
From: Tom Lane @ 2023-08-24 15:27 UTC (permalink / raw)
To: Andrew Dunstan <andrew@dunslane.net>; +Cc: pgsql-committers@lists.postgresql.org
Andrew Dunstan <andrew@dunslane.net> writes:
> Cache by-reference missing values in a long lived context
The v11 version of this patch is causing a compiler warning for me:
In file included from heaptuple.c:58:
heaptuple.c: In function 'missing_hash':
heaptuple.c:97:3: warning: implicit declaration of function 'hash_any'; did you mean 'hash_stats'? [-Wimplicit-function-declaration]
hash_any((const unsigned char *) entry->value, entry->len));
^~~~~~~~
../../../../src/include/postgres.h:471:38: note: in definition of macro 'DatumGetUInt32'
#define DatumGetUInt32(X) ((uint32) (X))
^
It seems to work anyway, but please fix.
regards, tom lane
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-24 20:36 Andrew Dunstan <andrew@dunslane.net>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 15+ messages in thread
From: Andrew Dunstan @ 2023-08-24 20:36 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-committers@lists.postgresql.org
On 2023-08-24 Th 11:27, Tom Lane wrote:
> Andrew Dunstan<andrew@dunslane.net> writes:
>> Cache by-reference missing values in a long lived context
> The v11 version of this patch is causing a compiler warning for me:
>
> In file included from heaptuple.c:58:
> heaptuple.c: In function 'missing_hash':
> heaptuple.c:97:3: warning: implicit declaration of function 'hash_any'; did you mean 'hash_stats'? [-Wimplicit-function-declaration]
> hash_any((const unsigned char *) entry->value, entry->len));
> ^~~~~~~~
> ../../../../src/include/postgres.h:471:38: note: in definition of macro 'DatumGetUInt32'
> #define DatumGetUInt32(X) ((uint32) (X))
> ^
>
> It seems to work anyway, but please fix.
Sorry about that, fixed.
While we're about it, let's also fix these warnings which are seen on my
systems building releases 11 and 12:
/home/andrew/bf/root/REL_11_STABLE/pgsql.build/../pgsql/src/backend/commands/foreigncmds.c:481:22:
warning: ‘funcargtypes’ may be used uninitialized [-Wmaybe-uninitialized]
/home/andrew/bf/root/REL_12_STABLE/pgsql.build/../pgsql/src/backend/commands/foreigncmds.c:487:22:
warning: ‘funcargtypes’ may be used uninitialized [-Wmaybe-uninitialized]
Maybe funcargtypes here should be initialized to { 0 } ?
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-24 20:57 Tom Lane <tgl@sss.pgh.pa.us>
parent: Andrew Dunstan <andrew@dunslane.net>
0 siblings, 1 reply; 15+ messages in thread
From: Tom Lane @ 2023-08-24 20:57 UTC (permalink / raw)
To: Andrew Dunstan <andrew@dunslane.net>; +Cc: pgsql-committers@lists.postgresql.org
Andrew Dunstan <andrew@dunslane.net> writes:
> On 2023-08-24 Th 11:27, Tom Lane wrote:
>> The v11 version of this patch is causing a compiler warning for me:
> Sorry about that, fixed.
Thanks!
> While we're about it, let's also fix these warnings which are seen on my
> systems building releases 11 and 12:
> /home/andrew/bf/root/REL_11_STABLE/pgsql.build/../pgsql/src/backend/commands/foreigncmds.c:481:22:
> warning: ‘funcargtypes’ may be used uninitialized [-Wmaybe-uninitialized]
> /home/andrew/bf/root/REL_12_STABLE/pgsql.build/../pgsql/src/backend/commands/foreigncmds.c:487:22:
> warning: ‘funcargtypes’ may be used uninitialized [-Wmaybe-uninitialized]
> Maybe funcargtypes here should be initialized to { 0 } ?
Hm. It looks like we got rid of those warnings in v13 via dcb7d3caf:
Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
Branch: master Release: REL_13_BR [dcb7d3caf] 2019-11-12 17:06:58 -0300
Have LookupFuncName accept NULL argtypes for 0 args
I'm a little tempted to propose that a better solution is to
back-patch that patch. Removing the warning alone doesn't make
a very strong case for that, but there are other arguments:
* Somebody might back-patch code relying on the newer convention;
* All else being equal, it's better to keep the code in different
branches looking similar.
I'm not sure if those arguments justify a back-patch instead of
the localized hack you suggest.
regards, tom lane
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-25 13:33 Andrew Dunstan <andrew@dunslane.net>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 15+ messages in thread
From: Andrew Dunstan @ 2023-08-25 13:33 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-committers@lists.postgresql.org
On 2023-08-24 Th 16:57, Tom Lane wrote:
> Andrew Dunstan<andrew@dunslane.net> writes:
>> On 2023-08-24 Th 11:27, Tom Lane wrote:
>>> The v11 version of this patch is causing a compiler warning for me:
>> Sorry about that, fixed.
> Thanks!
>
>> While we're about it, let's also fix these warnings which are seen on my
>> systems building releases 11 and 12:
>> /home/andrew/bf/root/REL_11_STABLE/pgsql.build/../pgsql/src/backend/commands/foreigncmds.c:481:22:
>> warning: ‘funcargtypes’ may be used uninitialized [-Wmaybe-uninitialized]
>> /home/andrew/bf/root/REL_12_STABLE/pgsql.build/../pgsql/src/backend/commands/foreigncmds.c:487:22:
>> warning: ‘funcargtypes’ may be used uninitialized [-Wmaybe-uninitialized]
>> Maybe funcargtypes here should be initialized to { 0 } ?
> Hm. It looks like we got rid of those warnings in v13 via dcb7d3caf:
>
> Author: Alvaro Herrera<alvherre@alvh.no-ip.org>
> Branch: master Release: REL_13_BR [dcb7d3caf] 2019-11-12 17:06:58 -0300
>
> Have LookupFuncName accept NULL argtypes for 0 args
>
> I'm a little tempted to propose that a better solution is to
> back-patch that patch. Removing the warning alone doesn't make
> a very strong case for that, but there are other arguments:
>
> * Somebody might back-patch code relying on the newer convention;
>
> * All else being equal, it's better to keep the code in different
> branches looking similar.
>
> I'm not sure if those arguments justify a back-patch instead of
> the localized hack you suggest.
>
>
Seems like overkill given the age of the surrounding code and the
nearness to EOL of releases 11 and 12.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-25 13:40 Tom Lane <tgl@sss.pgh.pa.us>
parent: Andrew Dunstan <andrew@dunslane.net>
0 siblings, 1 reply; 15+ messages in thread
From: Tom Lane @ 2023-08-25 13:40 UTC (permalink / raw)
To: Andrew Dunstan <andrew@dunslane.net>; +Cc: pgsql-committers@lists.postgresql.org
Andrew Dunstan <andrew@dunslane.net> writes:
> On 2023-08-24 Th 16:57, Tom Lane wrote:
>> I'm not sure if those arguments justify a back-patch instead of
>> the localized hack you suggest.
> Seems like overkill given the age of the surrounding code and the
> nearness to EOL of releases 11 and 12.
I agree that 11 is nearly dead, but 12 still has a year-plus to go.
Another point that I wasn't thinking of yesterday is that 11 is
still expected to compile on pre-C99 compilers. I'm not sure
to what extent we are still able to test that -- my old animals
have all gone to buildfarm heaven, although I see that Noah's
AIX menagerie is still soldiering on. Were we relying on "{ 0 }"
anywhere else pre-v12?
regards, tom lane
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-26 16:25 Alvaro Herrera <alvherre@alvh.no-ip.org>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 15+ messages in thread
From: Alvaro Herrera @ 2023-08-26 16:25 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Andrew Dunstan <andrew@dunslane.net>; pgsql-committers@lists.postgresql.org
On 2023-Aug-25, Tom Lane wrote:
> Another point that I wasn't thinking of yesterday is that 11 is
> still expected to compile on pre-C99 compilers. I'm not sure
> to what extent we are still able to test that -- my old animals
> have all gone to buildfarm heaven, although I see that Noah's
> AIX menagerie is still soldiering on. Were we relying on "{ 0 }"
> anywhere else pre-v12?
We have a few occurrences of {0} in initializations in pg11, so it
should work.
$ git grep '{\s*0\s*}' -- *.c
contrib/pgrowlocks/pgrowlocks.c: values[Atnum_xids] = "{0}";
contrib/pgrowlocks/pgrowlocks.c: values[Atnum_pids] = "{0}";
contrib/pgstattuple/pgstatapprox.c: output_type stat = {0};
contrib/pgstattuple/pgstattuple.c: pgstattuple_type stat = {0};
contrib/pgstattuple/pgstattuple.c: pgstattuple_type stat = {0};
src/backend/access/transam/xloginsert.c: XLogRecordBlockCompressHeader cbimg = {0};
src/backend/commands/explain.c: JitInstrumentation ji = {0};
src/backend/commands/explain.c: HashInstrumentation hinstrument = {0};
src/backend/commands/tablecmds.c: static Node bogus_marker = {0}; /* marks conflicting defaults */
src/backend/executor/execExpr.c: ExprEvalStep scratch = {0};
src/backend/executor/execExpr.c: ExprEvalStep scratch = {0};
src/backend/executor/execExpr.c: ExprEvalStep scratch = {0};
src/backend/executor/execExpr.c: ExprEvalStep scratch = {0};
src/backend/executor/execExpr.c: ExprEvalStep scratch = {0};
src/backend/executor/execExpr.c: ExprEvalStep scratch = {0};
src/backend/executor/execExpr.c: ExprEvalStep scratch2 = {0};
src/backend/executor/execExpr.c: ExprEvalStep scratch = {0};
src/backend/executor/execExpr.c: ExprEvalStep scratch = {0};
src/backend/regex/regcomp.c: /* postpone everything else pending possible {0} */
src/backend/regex/regcomp.c: /* annoying special case: {0} or {0,0} cancels everything */
src/backend/utils/adt/jsonfuncs.c: JsValue field = {0};
src/backend/utils/adt/jsonfuncs.c: JsValue jsv = {0};
src/backend/utils/adt/numeric.c:static const NumericDigit const_zero_data[1] = {0};
src/bin/pg_dump/pg_dump.c: "CASE WHEN pol.polroles = '{0}' THEN NULL ELSE "
src/bin/psql/describe.c: " || CASE WHEN polroles <> '{0}' THEN\n"
src/bin/psql/describe.c: " || CASE WHEN polroles <> '{0}' THEN\n"
src/bin/psql/describe.c: " CASE WHEN pol.polroles = '{0}' THEN NULL ELSE pg_catalog.array_to_string(array(select rolname from pg_catalog.pg_roles where oid = any (pol.polroles) order by 1),',') END,\n"
src/interfaces/ecpg/ecpglib/prepare.c:static stmtCacheEntry stmtCacheEntries[16384] = {{0, {0}, 0, 0, 0}};
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-26 21:41 Tom Lane <tgl@sss.pgh.pa.us>
parent: Alvaro Herrera <alvherre@alvh.no-ip.org>
0 siblings, 1 reply; 15+ messages in thread
From: Tom Lane @ 2023-08-26 21:41 UTC (permalink / raw)
To: Alvaro Herrera <alvherre@alvh.no-ip.org>; +Cc: Andrew Dunstan <andrew@dunslane.net>; pgsql-committers@lists.postgresql.org
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2023-Aug-25, Tom Lane wrote:
>> ... Were we relying on "{ 0 }"
>> anywhere else pre-v12?
> We have a few occurrences of {0} in initializations in pg11, so it
> should work.
Ah, indeed. Objection withdrawn then.
regards, tom lane
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: pgsql: Cache by-reference missing values in a long lived context
@ 2023-08-27 11:24 Andrew Dunstan <andrew@dunslane.net>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 15+ messages in thread
From: Andrew Dunstan @ 2023-08-27 11:24 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; Alvaro Herrera <alvherre@alvh.no-ip.org>; +Cc: pgsql-committers@lists.postgresql.org
On 2023-08-26 Sa 17:41, Tom Lane wrote:
> Alvaro Herrera<alvherre@alvh.no-ip.org> writes:
>> On 2023-Aug-25, Tom Lane wrote:
>>> ... Were we relying on "{ 0 }"
>>> anywhere else pre-v12?
>> We have a few occurrences of {0} in initializations in pg11, so it
>> should work.
> Ah, indeed. Objection withdrawn then.
>
>
OK, thanks, done.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
^ permalink raw reply [nested|flat] 15+ messages in thread
end of thread, other threads:[~2023-08-27 11:24 UTC | newest]
Thread overview: 15+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-08-22 19:17 pgsql: Cache by-reference missing values in a long lived context Andrew Dunstan <andrew@dunslane.net>
2023-08-22 19:17 pgsql: Cache by-reference missing values in a long lived context Andrew Dunstan <andrew@dunslane.net>
2023-08-22 19:17 pgsql: Cache by-reference missing values in a long lived context Andrew Dunstan <andrew@dunslane.net>
2023-08-22 19:17 pgsql: Cache by-reference missing values in a long lived context Andrew Dunstan <andrew@dunslane.net>
2023-08-22 19:17 pgsql: Cache by-reference missing values in a long lived context Andrew Dunstan <andrew@dunslane.net>
2023-08-22 19:18 pgsql: Cache by-reference missing values in a long lived context Andrew Dunstan <andrew@dunslane.net>
2023-08-23 21:22 pgsql: Cache by-reference missing values in a long lived context Andrew Dunstan <andrew@dunslane.net>
2023-08-24 15:27 ` Tom Lane <tgl@sss.pgh.pa.us>
2023-08-24 20:36 ` Andrew Dunstan <andrew@dunslane.net>
2023-08-24 20:57 ` Tom Lane <tgl@sss.pgh.pa.us>
2023-08-25 13:33 ` Andrew Dunstan <andrew@dunslane.net>
2023-08-25 13:40 ` Tom Lane <tgl@sss.pgh.pa.us>
2023-08-26 16:25 ` Alvaro Herrera <alvherre@alvh.no-ip.org>
2023-08-26 21:41 ` Tom Lane <tgl@sss.pgh.pa.us>
2023-08-27 11:24 ` Andrew Dunstan <andrew@dunslane.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox