From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
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 15:26:26 |
Message-ID: | 22694.1182525986@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl> writes:
> While trying to find a way to get indexed access to a table based on it's
> xmin, I ran into the following error message that seems a bit misleading:
> db=# select xmin || ' ' from <anytable> limit 1;
> ERROR: array value must start with "{" or dimension information
Yeah, it's being captured by the "anyelement || anyarray" operator for
lack of any other possible interpretation. We found a reasonable fix
for 8.3, in connection with removing implicit casts to text.
See long-running thread beginning here
http://archives.postgresql.org/pgsql-hackers/2007-02/msg01729.php
final solution invented beginning here
http://archives.postgresql.org/pgsql-hackers/2007-06/msg00116.php
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-06-22 17:07:09 | Re: BUG #3401: PITR does not work in the case ofrecovery_target_xid = 'SELECT_only_transaction_ID' |
Previous Message | Tom Lane | 2007-06-22 15:12:08 | Re: Temp table woes |