From: | "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Lista Postgres" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: psql does not save contents into file at end of command. |
Date: | 2006-12-27 17:47:43 |
Message-ID: | a97c77030612270947m5a5e8d5ai6e13653f0abf125@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 12/27/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)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;
i see . I did not investigate to that extent , i thought it was for all.
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.
Thanks for the notice
and belated Merry Christmas.
Regds
mallah.
regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2006-12-27 20:20:27 | Re: Dump and Query |
Previous Message | Joshua D. Drake | 2006-12-27 17:28:44 | Re: Importing from excelinto PostgreSQL |