From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heinemann, Manfred (IMS) <HeinemannM@imsweb.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: Function search_path
Date: Sun, 25 Mar 2018 13:13:31 -0400
Message-ID: <11207.1521998011@sss.pgh.pa.us> (raw)
In-Reply-To: <da2ee034500f4639b7c03b58f18f147a@THALASSA.omni.imsweb.com>
References: <db194d98f61d4aa398c1399a24326e7c@THALASSA.omni.imsweb.com>
<5f698c34-d01d-3196-1db4-75ba8f6a37d3@portavita.eu>
<b0078bdae3e04de1ba3ddaa3527c8922@THALASSA.omni.imsweb.com>
<2328.1521236730@sss.pgh.pa.us>
<da2ee034500f4639b7c03b58f18f147a@THALASSA.omni.imsweb.com>
"Heinemann, Manfred (IMS)" <HeinemannM@imsweb.com> writes:
> Here is an example where I can show significant extra memory consumption when setting search_path on a function:
I got around to testing this example today, and I don't see what you're
seeing --- the memory consumption seems stable, and about the same with
or without the "SET search_path" clause.
You didn't specify exactly how to do this bit:
--populate 1,000,000 rows with random values from 1,000 surnames for 'SURNAME'
so I did it like this:
INSERT INTO test_search_path(date_last_modified, last_name)
select clock_timestamp(), (random()*1000)::int::text
from generate_series(1,1000000);
The example doesn't seem like it'd be terribly data-dependent, but
maybe that's wrong?
Also, I assume you're running a reasonably up-to-date PG release,
otherwise I'd be wondering about leaks in the GIN index AM; we've
fixed some issues of that sort in GIN bulk updates in the past.
But again, it's not clear what the connection to a function SET
clause would be. So I lack a plausible theory at the moment.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, HeinemannM@imsweb.com, pgsql-admin@lists.postgresql.org
Subject: Re: Function search_path
In-Reply-To: <11207.1521998011@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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