Weird behavior in psql with \copy

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Weird behavior in psql with \copy
Date: 2006-11-24 16:39:08
Message-ID: 14A97C90424DEECFDABB2205@[172.26.14.247]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Folks,

following example shows a weird behavior with the transaction status
identifier
in psql's prompt and the \copy command:

bernd(at)[local]:bernd #= SELECT version();
version

------------------------------------------------------------------------------------------------------------------------------------
PostgreSQL 8.2beta3 on x86_64-unknown-linux-gnu, compiled by GCC gcc-4.0
(GCC) 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9)
(1 row)

bernd(at)[local]:bernd #= \set
AUTOCOMMIT = 'on'
PROMPT1 = '%n(at)%m:%/ %#%x%R '

[...]

bernd(at)[local]:bernd #= \copy foo TO '/home/bernd/tmp/test.dat'
bernd(at)[local]:bernd #*= COMMIT;
WARNING: there is no transaction in progress
COMMIT

I do the COMMIT; just to show that i'm really not in a transaction.

I see the same in PostgreSQL 8.1.4, too. It looks like get_prompt() seems
to fail to set the
correct prompt because PQtransactionStatus() still reports PGASYNC_BUSY,
but
i'm not that deep into libpq to nail that really down.

--
Thanks

Bernd

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2006-11-24 16:50:20 Re: Day and month name localization uses wrong locale category
Previous Message Tom Lane 2006-11-24 16:26:46 Re: Day and month name localization uses wrong locale category