From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rajesh Kumar Mallah <mallah.rajesh@gmail.com>
Cc: Lista Postgres <pgsql-admin@postgresql.org>
Subject: Re: psql does not save contents into file at end of command.
Date: Wed, 27 Dec 2006 11:27:06 -0500
Message-ID: <17970.1167236826@sss.pgh.pa.us> (raw)
In-Reply-To: <a97c77030612240218y46e955efyf31d0b5fd0836d11@mail.gmail.com>
References: <a97c77030612240218y46e955efyf31d0b5fd0836d11@mail.gmail.com>
"Rajesh Kumar Mallah" <mallah.rajesh@gmail.com> writes:
> tradein_clients=> \o db.lst
> tradein_clients=> \l (till this point, there is nothing in file db.lst)
> tradein_clients=> \q (now it saves) (also saves if another \o is issued)
> Dunno till what extent this behavior is justified.
I wasn't too excited about this, but on investigation, psql *does*
fflush() the \o file after each ordinary SQL command; it's only
backslash command output that doesn't necessarily reach the file
immediately. This is inconsistent ... if we're going to do it for
regular commands seems like we should do it for backslash commands
too.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, mallah.rajesh@gmail.com
Subject: Re: psql does not save contents into file at end of command.
In-Reply-To: <17970.1167236826@sss.pgh.pa.us>
References: <a97c77030612240218y46e955efyf31d0b5fd0836d11@mail.gmail.com> <17970.1167236826@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox