Re: Change RangeVarGetRelidExtended() to take flags argument?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org
Date: 2018-03-06T00:57:44Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > One wrinkle in that plan is that it'd not be trivial to discern whether > a lock couldn't be acquired or whether the object vanished. I don't > really have good idea how to tackle that yet. Do we really care which case applies? But having to mess with the semantics of RangeVarGetRelidExtended seems like a good reason not to go down this path... regards, tom lane
Commits
-
Add SKIP_LOCKED option to RangeVarGetRelidExtended().
- 3e256e550672 11.0 landed
-
Combine options for RangeVarGetRelidExtended() into a flags argument.
- d87510a524f3 11.0 landed