From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | "Doom(dot)zhou" <zzepaigh(at)gmail(dot)com> |
Cc: | David Johnston <polobo(at)yahoo(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Notice about psql ! |
Date: | 2013-12-18 02:58:42 |
Message-ID: | 20131218025842.GB6509@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Dec 18, 2013 at 10:35:33AM +0800, Doom.zhou wrote:
> Really thanks
>
>
> On Tue, Dec 17, 2013 at 11:04 PM, David Johnston <polobo(at)yahoo(dot)com> wrote:
>
> Steve Crawford wrote
> > On 12/16/2013 09:29 PM, Doom.zhou wrote:
> >> HI guys
> >> when edit some sql in psql's \e feature then quit edit
> >> it is performed !!!!
> >>
> >>
> >> it's dangerous isn't it ?
> >>
> > It is *extremely* dangerous. But neither more nor less dangerous than
> > any interface that allows you to submit SQL directly to the server.
> >
> > The \e command merely offers an alternative to the command-line editing
> > to craft your SQL statements and is very convenient when you are editing
> > a long statement. When done, you exit and the command is submitted just
> > as it is submitted when you press
> > <Enter>
> > at the command-line.
> >
> > If you change your mind while in the editor, just clear the text in the
> > editor and exit. Nothing will be run.
>
> Or
>
> BEGIN; <Enter>
>
> \e <Enter>
>
> COMMIT | ROLLBACK ; <Enter>
Actually, just remove the semicolon from the query and it will not run
when you exit \e.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Doom.zhou | 2013-12-18 06:19:04 | Re: script to drop and create all indexes in a database with parameter concurrently |
Previous Message | Doom.zhou | 2013-12-18 02:35:33 | Re: Notice about psql ! |