Skip site navigation (1) Skip section navigation (2)

Re: Error message that is a bit misleading / weird result from <xid> || null

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Frank van Vugt" <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Error message that is a bit misleading / weird result from <xid> || null
Date: 2007-06-22 13:22:53
Message-ID: 87645gp1hu.fsf@oxford.xeocode.com (view raw or flat)
Thread:
Lists: pgsql-bugs
"Frank van Vugt" <ftm(dot)van(dot)vugt(at)foxi(dot)nl> writes:

> Sidenote: since it does solve my problem, I can now build an index based on 
> such an interpretation of xmin, I'm a bit anxious as to how this will 
> be 'fixed', if at all ;)

Actually this was noticed only recently but that was precisely because it was
related to some significant changes that were being made. Because of those
changes 8.3 behaves markedly different in this area:

postgres=# select xmin || 'x' from w limit 1;
 ?column? 
----------
 1679x
(1 row)

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com


In response to

pgsql-bugs by date

Next:From: Zdenek KotalaDate: 2007-06-22 13:30:44
Subject: Re: BUG #3403: ver 8.2 can't add serial column to temp table,but 8.1 can
Previous:From: Frank van VugtDate: 2007-06-22 13:08:26
Subject: Error message that is a bit misleading / weird result from <xid> || null

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group