Re: [HACKERS] Status report: long-query-string changes - Mailing list pgsql-hackers

From Leon
Subject Re: [HACKERS] Status report: long-query-string changes
Date
Msg-id 37DCFD90.942065B4@udmnet.ru
Whole thread Raw
In response to Status report: long-query-string changes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Status report: long-query-string changes  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.



pgsql-hackers by date:

Previous
From: Leon
Date:
Subject: Re: [HACKERS] Status report: long-query-string changes
Next
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] Re: pgaccess update for 6.5.2?