encoding problems

From: Cliff Nieuwenhuis <cliff(at)nieusite(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: encoding problems
Date: 2008-03-11 15:10:15
Message-ID: 200803111010.15629.cliff@nieusite.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-novice pgsql-patches

I'm not sure how to ask this question. I have written a function, and with
PostgreSQL 8.0.13 I can do a "\df+" and see something like this under Source
Code:

DECLARE
result text;
BEGIN
result := (SELECT SUBSTRING(fname FROM 1 FOR 1) ||
SUBSTRING(mname FROM 1 FOR 1) ||
SUBSTRING(lname FROM 1 FOR 1)
FROM employees WHERE id = empid);
RETURN result;
END;

If I create the same function on my computer running PostgreSQL 8.3.0 and try
the \df+ then the Source Code shows:

\x09DECLARE

\x09\x09result text;
:
\x09
:
\x09BEGIN
:
\x09\x09result := (SELECT SUBSTRING(fname FROM 1 FOR 1) ||
:
\x09\x09\x09\x09\x09\x09SUBSTRING(mname FROM 1 FOR 1) ||
:
\x09\x09\x09\x09\x09\x09SUBSTRING(lname FROM 1 FOR 1)
:
\x09\x09\x09\x09\x09\x09FROM employees WHERE id = empid);
:
\x09\x09RETURN result;
:
\x09END;

I've tried changing the database encoding and some other things, but can't
seem to fix this.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-03-11 15:17:23 Re: LISTEN vs. two-phase commit
Previous Message Magnus Hagander 2008-03-11 15:09:38 Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severity to PGconn return status > >

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2008-03-11 16:41:35 Re: [NOVICE] encoding problems
Previous Message kenneth d'souza 2008-03-11 11:04:50 Checkpoint ; WAL

Browse pgsql-patches by date

  From Date Subject
Next Message Zdenek Kotala 2008-03-11 16:07:30 Re: [PATCHES] Fix for large file support (nonsegment mode support)
Previous Message Tom Lane 2008-03-11 14:48:59 Re: [PATCHES] Fix for large file support (nonsegment mode support)