Re: Largeobject Access Controls (r2460) - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Largeobject Access Controls (r2460)
Date
Msg-id 4B5D782C020000250002EB76@gw.wicourts.gov
Whole thread Raw
In response to Re: Largeobject Access Controls (r2460)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> It might be better to try a test case with lighter-weight objects,
> say 5 million simple functions.
A dump of that quickly settled into running a series of these:
SELECT proretset, prosrc, probin,
pg_catalog.pg_get_function_arguments(oid) AS funcargs,
pg_catalog.pg_get_fun
ction_identity_arguments(oid) AS funciargs,
pg_catalog.pg_get_function_result(oid) AS funcresult, proiswindow,
provolatile, proisstrict, prosecdef, proconfig, procost, prorows, (S
ELECT lanname FROM pg_catalog.pg_language WHERE oid = prolang) AS
lanname FROM pg_catalog.pg_proc WHERE oid =
'1404528'::pg_catalog.oid
(with different oid values, of course).
Is this before or after the point you were worried about.  Anything
in particular for which I should be alert?
-Kevin


pgsql-hackers by date:

Previous
From: "Ross J. Reedstrom"
Date:
Subject: Re: MySQL-ism help patch for psql
Next
From: "Ross J. Reedstrom"
Date:
Subject: Re: MySQL-ism help patch for psql