Re: Capturing pgsql ERRORS/NOTICES to file

I am in the process of creating a batch file that will update some functions in a database for a remote user similar to:

psql -o output dbname < functionupdate.sql

Is there any way to save any ERROR and NOTICE messages to a file?

The -o option doesn't capture this information.

Thanks,
George

George,

> I am in the process of creating a batch file that will update some
> functions in a database for a remote user similar to:
>
> psql -o output dbname < functionupdate.sql
>
> Is there any way to save any ERROR and NOTICE messages to a file?
>
> The -o option doesn't capture this information.

You have to use command shell redirects.

For example, I commonly do in bash
psql -o output dbname < functionupdate.sql >out.dump
... which sends all the command responses to a file, allowing me to read only
the errors on the screen.

See a guide to your shell for more creative redirection.

--
Josh Berkus
Aglio Database Solutions
San Francisco

Hi Josh,

Thanks for the reply.

What I am trying to achieve is to have errors go to a file, rather than show
up on the screen.

Is this possible?

George

----- Original Message -----
From: "Josh Berkus" <josh(at)agliodbs(dot)com>
To: "George Weaver" <georgew1(at)mts(dot)net>; <pgsql-sql(at)postgresql(dot)org>
Sent: Friday, September 26, 2003 1:33 PM
Subject: Re: [SQL] Capturing pgsql ERRORS/NOTICES to file

> George,
>
> > I am in the process of creating a batch file that will update some
> > functions in a database for a remote user similar to:
> >
> > psql -o output dbname < functionupdate.sql
> >
> > Is there any way to save any ERROR and NOTICE messages to a file?
> >
> > The -o option doesn't capture this information.
>
> You have to use command shell redirects.
>
> For example, I commonly do in bash
> psql -o output dbname < functionupdate.sql >out.dump
> ... which sends all the command responses to a file, allowing me to read
only
> the errors on the screen.
>
> See a guide to your shell for more creative redirection.
>
> --
> Josh Berkus
> Aglio Database Solutions
> San Francisco
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>

George:

Have you tried psql {whatever operations} 2> error_output ?

(for Bash)

Thanks

Wei

On Fri, 26 Sep 2003, George Weaver wrote:

> Hi Josh,
>
> Thanks for the reply.
>
> What I am trying to achieve is to have errors go to a file, rather than show
> up on the screen.
>
> Is this possible?
>
> George
>
> ----- Original Message -----
> From: "Josh Berkus" <josh(at)agliodbs(dot)com>
> To: "George Weaver" <georgew1(at)mts(dot)net>; <pgsql-sql(at)postgresql(dot)org>
> Sent: Friday, September 26, 2003 1:33 PM
> Subject: Re: [SQL] Capturing pgsql ERRORS/NOTICES to file
>
>
> > George,
> >
> > > I am in the process of creating a batch file that will update some
> > > functions in a database for a remote user similar to:
> > >
> > > psql -o output dbname < functionupdate.sql
> > >
> > > Is there any way to save any ERROR and NOTICE messages to a file?
> > >
> > > The -o option doesn't capture this information.
> >
> > You have to use command shell redirects.
> >
> > For example, I commonly do in bash
> > psql -o output dbname < functionupdate.sql >out.dump
> > ... which sends all the command responses to a file, allowing me to read
> only
> > the errors on the screen.
> >
> > See a guide to your shell for more creative redirection.
> >
> > --
> > Josh Berkus
> > Aglio Database Solutions
> > San Francisco
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 2: you can get off all lists at once with the unregister command
> > (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>

Hi Wei,

I hadn't tried that, and it did the trick!

Thank you!

George

----- Original Message -----
From: "Wei Weng" <wweng(at)kencast(dot)com>
To: "George Weaver" <georgew1(at)mts(dot)net>
Cc: <pgsql-sql(at)postgresql(dot)org>
Sent: Friday, September 26, 2003 2:16 PM
Subject: Re: [SQL] Capturing pgsql ERRORS/NOTICES to file

> George:
>
> Have you tried psql {whatever operations} 2> error_output ?
>
> (for Bash)
>
> Thanks
>
> Wei
>
>
> On Fri, 26 Sep 2003, George Weaver wrote:
>
> > Hi Josh,
> >
> > Thanks for the reply.
> >
> > What I am trying to achieve is to have errors go to a file, rather than
show
> > up on the screen.
> >
> > Is this possible?
> >
> > George
> >
> > ----- Original Message -----
> > From: "Josh Berkus" <josh(at)agliodbs(dot)com>
> > To: "George Weaver" <georgew1(at)mts(dot)net>; <pgsql-sql(at)postgresql(dot)org>
> > Sent: Friday, September 26, 2003 1:33 PM
> > Subject: Re: [SQL] Capturing pgsql ERRORS/NOTICES to file
> >
> >
> > > George,
> > >
> > > > I am in the process of creating a batch file that will update some
> > > > functions in a database for a remote user similar to:
> > > >
> > > > psql -o output dbname < functionupdate.sql
> > > >
> > > > Is there any way to save any ERROR and NOTICE messages to a file?
> > > >
> > > > The -o option doesn't capture this information.
> > >
> > > You have to use command shell redirects.
> > >
> > > For example, I commonly do in bash
> > > psql -o output dbname < functionupdate.sql >out.dump
> > > ... which sends all the command responses to a file, allowing me to
read
> > only
> > > the errors on the screen.
> > >
> > > See a guide to your shell for more creative redirection.
> > >
> > > --
> > > Josh Berkus
> > > Aglio Database Solutions
> > > San Francisco
> > >
> > > ---------------------------(end of
broadcast)---------------------------
> > > TIP 2: you can get off all lists at once with the unregister command
> > > (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)or
g)
> > >
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 9: the planner will ignore your desire to choose an index scan if
your
> > joining column's datatypes do not match
> >
>