Re: BUG #7635: psql -1 and \connect

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgmail(at)joh(dot)to
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7635: psql -1 and \connect
Date: 2012-11-01 21:29:50
Message-ID: 7960.1351805390@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

pgmail(at)joh(dot)to writes:
> I know it's not clear what to do with --single-transaction if a script is
> \connecting to multiple databases in a single file, but IMHO it should at
> least work correctly for the single database case.

Define "correctly" --- I would expect \connect to establish a new
connection even if the same target database is named. We can't change
that behavior without breaking existing scripts, IMO --- for example, \c
is a long-established way to reset GUC settings, prepared statements,
etc.

Perhaps we should have \connect fail outright in -1 mode. I can see
no way for it to do anything and still maintain the expectation of a
single transaction.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Marko Tiikkaja 2012-11-01 22:05:57 Re: BUG #7635: psql -1 and \connect
Previous Message abaile33 2012-11-01 21:13:10 BUG #7637: postgres92-9.2.1-1.x86_64 requires libuuid.so.16()(64bit)