Re: AW: Questionable coding in proc.c & lock.c - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: AW: Questionable coding in proc.c & lock.c
Date
Msg-id 398ECFBC.FAAA9920@alumni.caltech.edu
Whole thread Raw
In response to AW: Questionable coding in proc.c & lock.c  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
List pgsql-hackers
> > > ... was considering doing a hack in
> > > analyze.c which just plops a "BEGIN" in front of the
> > existing query.
> Wouldn't the hack be to issue a begin work after connect,
> and then issue begin work after each commit or rollback ?

Sure. When hacking all things are possible ;)

But I do have some preference for not doing work until something is
requested (not me personally, but in the code) so would prefer to issue
the BEGIN at the first query.
                    - Thomas


pgsql-hackers by date:

Previous
From: Zeugswetter Andreas SB
Date:
Subject: AW: Now PostgreSQL recovers from errors within trns
Next
From: "Mark Hollomon"
Date:
Subject: 'GROUP BY' / 'DISTINCT' interaction bug?