pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <maillist@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org <pgsql-hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: HISTORY for 6.5.2
Date: Mon, 13 Sep 1999 21:03:04 -0400 (EDT)
Message-ID: <199909140103.VAA06678@candle.pha.pa.us> (raw)
In-Reply-To: <11056.937256188@sss.pgh.pa.us>

> And I can't take credit for that either --- Hiroshi and/or Tatsuo get
> the credit, IIRC.  (BTW, did we patch those into 6.5.*, or only 6.6?)
> 
> >        Update frontend libpq to remove limits on query lengths,
> >        error/notice message lengths, and number of fields per tuple(Tom)
> 
> This is *not* in 6.5.*, only 6.6.

I have:
	
	RCS file: /usr/local/cvsroot/pgsql/src/interfaces/libpq/pqexpbuffer.c,v
	Working file: src/interfaces/libpq/pqexpbuffer.c
	head: 1.1
	branch:
	locks: strict
	access list:
	symbolic names:
	keyword substitution: kv
	total revisions: 1;     selected revisions: 1
	description:
	----------------------------
	revision 1.1
	date: 1999/08/31 01:37:37;  author: tgl;  state: Exp;
	Update frontend libpq to remove limits on query lengths,
	error/notice message lengths, and number of fields per tuple.  Add
	pqexpbuffer.c/.h, a frontend version of backend's stringinfo module.
	This is first step in applying Mike Ansley's long-query patches,
	even though he didn't do any of these particular changes...

Seems addition of text files shows up in all branches, which I guess
makes sense.  No cause for alarm.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



view thread (62+ messages)  latest in thread

Message-ID: <199909140103.VAA06678@candle.pha.pa.us>
Permalink:  ../199909140103.VAA06678@candle.pha.pa.us/
Also on:    postgresql.org/message-id/199909140103.VAA06678@candle.pha.pa.us

 · 

reply

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: maillist@candle.pha.pa.us, tgl@sss.pgh.pa.us
  Subject: Re: [HACKERS] Re: HISTORY for 6.5.2
  In-Reply-To: <199909140103.VAA06678@candle.pha.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