From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <maillist@candle.pha.pa.us>
Cc: hackers@postgreSQL.org
Subject: Re: [HACKERS] Open 6.4 items
Date: Mon, 24 Aug 1998 21:01:18 -0400
Message-ID: <25977.904006878@sss.pgh.pa.us> (raw)
In-Reply-To: <199808240208.WAA09755@candle.pha.pa.us>
Bruce Momjian <maillist@candle.pha.pa.us> writes:
> With the 6.4 beta just over a week away, here are the open items I see
> for 6.4. We actually have fewer than usual, so that is a good thing.
I had a few other things on my list:
* make PGconn,PGresult truly opaque to applications (per recent discussion)
* libpgtcl is missing any way to access PQerrorMessage!?
* remove writable fields in static PQconninfoOptions for thread safety
* bring libpq.sgml documentation fully up to speed
(I'm willing to do the above four, but am not promising that the doco
will get done before Sept 1. I think Thomas indicated that Sept 15
is OK for docs?)
* put UNLISTEN in standard backend, fix libpgtcl listen support to use it
I would really like to see this in 6.4, because I need UNLISTEN in my
applications. Thomas had volunteered to add the needed parser support
for UNLISTEN (the execution function already exists, it just needs a
statement that can call it). As far as I've heard he hasn't gotten to
it yet. I can fix libpgtcl but do not want to touch it unless the
underlying backend support is there.
* psql: control-c ought to stop lengthy output
* psql's \z output truncates table names at 16 chars
* psql and libpgtcl insert unexpected backslashes in output data
I was going to work on these but it's looking like they will not make
the Sept 1 cut. Anyone else want to do them?
> change pg args for platforms that don't support argv changes
> (setproctitle()?, sendmail hack?)
I'd like to see this in there too, and will work on it if no one else
does, but I rather doubt I can get to it by Sept 1. Maybe this will
have to wait for 6.5, or 6.4.1, or something.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, maillist@candle.pha.pa.us, hackers@postgreSQL.org
Subject: Re: [HACKERS] Open 6.4 items
In-Reply-To: <25977.904006878@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox