Adrian Klaver-4 wrote
> On 10/20/2014 12:03 PM, Tom Lane wrote:
>> Victor Yegorov <
> vyegorov@
> > writes:
>>> 2014-10-20 21:43 GMT+03:00 Adrian Klaver <
> adrian.klaver@
> >:
With \set AUTOCOMMIT off the COMMIT ended one transaction block and
started another.
>>
>>> I don't think `C
On 10/20/2014 12:03 PM, Tom Lane wrote:
Victor Yegorov writes:
2014-10-20 21:43 GMT+03:00 Adrian Klaver :
With \set AUTOCOMMIT off the COMMIT ended one transaction block and
started another.
I don't think `COMMIT` starts a new transaction block here,
as I can run `VACUUM` after it, and vacu
On 10/20/2014 12:03 PM, Tom Lane wrote:
Victor Yegorov writes:
2014-10-20 21:43 GMT+03:00 Adrian Klaver :
With \set AUTOCOMMIT off the COMMIT ended one transaction block and
started another.
I don't think `COMMIT` starts a new transaction block here,
as I can run `VACUUM` after it, and vacu
Victor Yegorov writes:
> 2014-10-20 21:43 GMT+03:00 Adrian Klaver :
>> With \set AUTOCOMMIT off the COMMIT ended one transaction block and
>> started another.
> I don't think `COMMIT` starts a new transaction block here,
> as I can run `VACUUM` after it, and vacuum also cannot be run inside
> tra
2014-10-20 21:43 GMT+03:00 Adrian Klaver :
> With \set AUTOCOMMIT off the COMMIT ended one transaction block and
> started another.
I don't think `COMMIT` starts a new transaction block here,
as I can run `VACUUM` after it, and vacuum also cannot be run inside
transaction block.
--
Victor Y.
On 10/20/2014 11:30 AM, Victor Yegorov wrote:
Greetings.
I'm observing the following on 9.3.5 and also on 9.4beta3:
\set AUTOCOMMIT on
CREATE TYPE enum_type AS ENUM ('bad', 'good');
CREATE TYPE
ALTER TYPE enum_type ADD VALUE 'so-so' AFTER 'bad';
ALTER TYPE
DROP TYPE enum_type;
DROP TYPE;
\set
