Re: [HACKERS] Status report: long-query-string changes

From: Leon <leon(at)udmnet(dot)ru>
To: hackers <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Status report: long-query-string changes
Date: 1999-09-13 13:35:12
Message-ID: 37DCFD90.942065B4@udmnet.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Lockhart wrote:
>
> > Thomas Lockhart should speak up...
> > He knows he'll never have to answer for any of his theories actually
> > being put to test. If they were, they would be contaminated by reality.
>
> You talkin' to me?? ;)

Nein, nein! Sei still bitte! :) This is my signature which is a week
old already :)

> A simple fix would be to check the current size after lexing of that
> accumulated string buffer, and if it is non-zero then elog(ERROR) a
> complaint. Perhaps a more general fix would be to ensure that you are
> never in an exclusive state after all tokens are processed, but I'm
> not sure how to do that.

The solution is obvious - to eliminate exclusive states entirely!
Banzai!!!

--
Leon.
-------
He knows he'll never have to answer for any of his theories actually
being put to test. If they were, they would be contaminated by reality.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 1999-09-13 14:05:25 Re: [HACKERS] Re: pgaccess update for 6.5.2?
Previous Message Leon 1999-09-13 13:34:56 Re: [HACKERS] Status report: long-query-string changes