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

Re: Bug #728: Interactions between bytea and character encoding when doing analyze

From: Anders Hammarquist <iko(at)strakt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #728: Interactions between bytea and character encoding when doing analyze
Date: 2002-08-02 10:34:06
Message-ID: 200208021034.g72AY717024386@fido.strakt.com (view raw or flat)
Thread:
Lists: pgsql-bugs
> pgsql-bugs(at)postgresql(dot)org writes:
> > If a byte string that is not valid unicode is inserted into a bytea
> > column, analyze will fail unless the data was tagged as bytea in the
> > insert.
> 
> Your example produces no failure for me.  You'd better be more specific
> about which PG version you're running, on what platform, with what
> configure options and what database encoding, etc.

Ah, sorry about that. It's 7.2.1, in the Debian package incarnation
7.2.1-2. The database and the client encoding are both unicode. These
are the setting from postmaster.conf (nothing strange):

debug_level = 0
log_connections = on
log_pid = on
log_timestamp = on
syslog = 2
silent_mode = off
syslog_facility = LOCAL0
trace_notify = off
max_connections = 64
shared_buffers = 128
tcpip_socket = 1
stats_start_collector = on
stats_reset_on_server_start = off
stats_command_string = on
stats_block_level = on
stats_row_level = on

/Anders


In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2002-08-02 14:04:26
Subject: Re: [PORTS] make check fails -- 8 hour time difference in old dates
Previous:From: Olcsák JózsefDate: 2002-08-02 07:19:54
Subject: TEMP TABLE USING PROBLEM

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