Re: AW: Questionable coding in proc.c & lock.c

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: AW: Questionable coding in proc.c & lock.c
Date: 2000-08-07 15:03:24
Message-ID: 398ECFBC.FAAA9920@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Hollomon 2000-08-07 15:07:03 'GROUP BY' / 'DISTINCT' interaction bug?
Previous Message Zeugswetter Andreas SB 2000-08-07 13:50:20 AW: Now PostgreSQL recovers from errors within trns