On 12/29/12 3:36 PM, Stephen Frost wrote:
Perhaps there's a better way to handle that?
Responding to feedback would be a nice start. This submissions has been
dead at "Waiting on Author" for at least 3 months now. Time to give it
the "Returned with Feedback" boot and see if it comes around
Alastair,
* Alastair Turner (b...@ctrlf5.co.za) wrote:
> Patch for the changes discussed in
> http://archives.postgresql.org/pgsql-hackers/2010-10/msg00919.php
> attached (eventually ...)
>
> In summary: If the input file (-f) doesn't exist or the ouput or log
> files (-o and -l) can't be created
Josh,
* Josh Kupershmidt (schmi...@gmail.com) wrote:
> I assume you meant "-L" instead of "-l" here for specifying psql's log
> file. I don't think that the inability to write to psql's log file
> should be treated as a fatal error, especially since it is not treated
> as such by the current code:
On Sun, Dec 2, 2012 at 4:37 AM, Alastair Turner wrote:
> Patch for the changes discussed in
> http://archives.postgresql.org/pgsql-hackers/2010-10/msg00919.php
> attached (eventually ...)
>
> In summary: If the input file (-f) doesn't exist or the ouput or log
> files (-o and -l) can't be created
On Sun, Dec 2, 2012 at 6:37 AM, Alastair Turner wrote:
> Patch for the changes discussed in
> http://archives.postgresql.org/pgsql-hackers/2010-10/msg00919.php
> attached (eventually ...)
>
> In summary: If the input file (-f) doesn't exist or the ouput or log
> files (-o and -l) can't be created
Patch for the changes discussed in
http://archives.postgresql.org/pgsql-hackers/2010-10/msg00919.php
attached (eventually ...)
In summary: If the input file (-f) doesn't exist or the ouput or log
files (-o and -l) can't be created psql exits before prompting for a
password.
Regards,
Alastair.
