I sit corrected.
*slightly humbled*
Why not do an unsigned int16 to hold your UUID generated numbers. Ultimately,
this would seem to be a more general solution and accomplish your goals at
the sametime. Or, am I completely missing something.
Christopher Kings-Lynne wrote:
don't c
Alex Pilosov <[EMAIL PROTECTED]> writes:
> I'm done with change of RangeTblEntry into three different node types:
> RangeTblEntryRelation,RangeTblEntrySubSelect,RangeTblEntryPortal which
> have different fields. All the existing places instead of using
> rte->subquery to determine type now use IsA
I have been making some notes about the rules for accessing shared disk
buffers, since they aren't spelled out anywhere now AFAIK. In process
I found what seems to be a nasty bug in the code that tries to build
btree indexes that include already-dead tuples. (If memory serves,
Hiroshi added that
On Tue, 22 May 2001, Bruce Momjian wrote:
> I am always confused when to bump the minor and when the major. I also
> was not sure how significant the change would be for apps. We added
> const, and I changed the return type of one function from short to int.
> Seems like ConnectionBad was also
Peter Eisentraut wrote:
Dmitry G. Mastrukov writes:
I've developed new data type for PostgreSQL - unique identifier - 128-bitvalue claims to be unique across Universe. It depends on libuuid frome2fsprogs by Theodore Ts'o.
ISTM that this should be a function, not a data type.
