Re: [GENERAL] GUID/UUID Support

2007-01-18 Thread Patrick Earl
#x27;t map nicely to those higher level types. Patrick On 1/17/07, Chad Wagner <[EMAIL PROTECTED]> wrote: On 1/17/07, Patrick Earl <[EMAIL PROTECTED]> wrote: > Certainly support for the GUID field type itself is most important. > As for the generators, though they are

Re: [GENERAL] GUID/UUID Support

2007-01-17 Thread Patrick Earl
While using third party modules is not really a barrier for people deep in the PostgreSQL world, here is what I would need to do to use GUIDs today. 1. Get a set of GUID/UUID patches (there seem to be many) and recompile the necessary code. 2. Do the same thing for Windows, assuming that the pa

[GENERAL] GUID/UUID Support

2007-01-16 Thread Patrick Earl
Greetings all. I've been poking around the web and trying to track the status of the GUID/UUID patches. In the todo list, that item is not marked as going into 8.3, and I feel this is unfortunate. Searching google for "postgresql guid -guide" comes up with around 200,000 hits. It's obviously b

Re: [GENERAL] Checkpoint request failed on version 8.2.1.

2007-01-11 Thread Patrick Earl
unit tests remove all contents and schema within the database before starting, and they remove the tables they create as they proceed. Certainly there are many things have been recently deleted. Patrick On 1/11/07, Tom Lane <[EMAIL PROTECTED]> wrote: "Patrick Earl" <[

Re: [GENERAL] Checkpoint request failed on version 8.2.1.

2007-01-11 Thread Patrick Earl
reate database command using pgadmin. We are logging into PostgreSQL as the same user. Patrick On 1/11/07, Tom Lane <[EMAIL PROTECTED]> wrote: "Patrick Earl" <[EMAIL PROTECTED]> writes: > 2007-01-11 09:56:17 ERROR: could not open relation 1663/16403/16426: >

[GENERAL] Checkpoint request failed on version 8.2.1.

2007-01-11 Thread Patrick Earl
Hi all. I'm getting a checkpoint request failed message when I try to execute a CREATE DATABASE command. Since it was a fresh install, I've included the entire server log up to the point of the error. I truncated the log output two lines after the error message. Is there a way I can avoid this