Re: Error message that is a bit misleading / weird result from || null - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Error message that is a bit misleading / weird result from || null
Date
Msg-id 22694.1182525986@sss.pgh.pa.us
Whole thread Raw
In response to Error message that is a bit misleading / weird result from || null  (Frank van Vugt <ftm.van.vugt@foxi.nl>)
List pgsql-bugs
Frank van Vugt <ftm.van.vugt@foxi.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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Temp table woes
Next
From: Tom Lane
Date:
Subject: Re: BUG #3401: PITR does not work in the case ofrecovery_target_xid = 'SELECT_only_transaction_ID'