Re: [ADMIN] maximum attribute record.

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Jan Kim <kim(at)mpiz-koeln(dot)mpg(dot)de>
Cc: Vikrant Rathore <vikrant(at)chemquick(dot)com>, Postgres GOD <postgres(at)pili(dot)adn(dot)edu(dot)ph>, pgsql-admin(at)postgreSQL(dot)org, PostgreSQL-development <hackers(at)postgreSQL(dot)org>
Subject: Re: [ADMIN] maximum attribute record.
Date: 1999-05-09 11:53:57
Message-ID: 199905091153.HAA16470@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Has this been fixed in 6.5 beta?

> On Tue, Feb 02, 1999 at 07:33:48PM +0800, Vikrant Rathore wrote:
>
> > If your query is bigger than 8192 bytes then libpq simply truncates it
> > without giving any warning
>
> I've read that in the docs, too (while back, didn't try it out). I have
> to say, though, that I think this behaviouur is somewhat less than optimal.
> Personally, I strongly prefer it if error conditions are raised by software
> when it isn't able to carry out the requested function.

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

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-05-09 11:54:58 Re: [HACKERS] 6.5 beta and ORDER BY patch
Previous Message Bruce Momjian 1999-05-09 11:14:17 Re: [SQL] Re: [HACKERS] Re: INSERT/UPDATE waiting (another example)