Re: Can avoid list_copy in recomputeNamespacePath() conditionally?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: amul sul <sulamul(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Can avoid list_copy in recomputeNamespacePath() conditionally?
Date: 2019-11-02 14:31:14
Message-ID: 19685.1572705074@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

amul sul <sulamul(at)gmail(dot)com> writes:
> I wondered can we have a shortcut somewhat similar to following POC
> in recomputeNamespacePath () when the recomputed path is the same as the
> previous baseSearchPath/activeSearchPath :
> + /* TODO: POC */
> + if (equal(oidlist, baseSearchPath))
> + return;

There's an awful lot missing from that sketch; all of the remaining
steps still need to be done:

baseCreationNamespace = firstNS;
baseTempCreationPending = temp_missing;

/* Mark the path valid. */
baseSearchPathValid = true;
namespaceUser = roleid;

/* And make it active. */
activeSearchPath = baseSearchPath;
activeCreationNamespace = baseCreationNamespace;
activeTempCreationPending = baseTempCreationPending;

/* Clean up. */
pfree(rawname);
list_free(namelist);
list_free(oidlist);

More to the point, I think the onus would be on the patch submitter
to prove that the extra complexity had some measurable benefit.
I really doubt that it would, since the list_copy is surely trivial
compared to the catalog lookup work we had to do to compute the OID
list above here.

It'd likely be more useful to see if you could reduce the number of
places where we have to invalidate the path in the first place.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-11-02 14:36:56 Re: alternative to PG_CATCH
Previous Message Antonin Houska 2019-11-02 12:34:41 Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)