Conrad Lender writes:
> I looked into the startup scripts that are used here (Ubuntu 8.10):
> ...
> The pg_ctlcluster script parses postgresql.conf and, if log_filename and
> log_directory aren't defined there, adds '-l
> /var/log/postgresql/postgresql-8.3-main.log' as an option for pg_ctl.
> This
On 08/05/09 16:43, Conrad Lender wrote:
> stderr to stdin to capture warnings and errors:
That should be "stderr to stdout", of course.
- Conrad
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
On 07/05/09 18:26, Tom Lane wrote:
> Scott Mead writes:
>> How did you restart postgres? I'm guessing that you're using a
>> distribution provided package. If you're using the /etc/init.d
>> scripts from that package, it's likely that the startup script is
>> redirecting stderr and that the syst
Scott Mead writes:
> On Thu, May 7, 2009 at 11:29 AM, Conrad Lender wrote:
>> When I leave both log_directory and log_filename commented out (my
>> original settings), then restart postgres, it creates the file
>>
>> /var/log/postgresql/postgresql-8.3-main.log
>>
>> This contains three lines ab
On Thu, May 7, 2009 at 11:29 AM, Conrad Lender wrote:
>
> I'm beginning to feel incredibly dense now, but this actually brought my
> original problem back. When I do specify log_filename and log_directory,
> and restart Postgres, the test you suggested ('select 1/0;') shows up as
> an error in th
On 07/05/09 16:56, Adrian Klaver wrote:
>> The server startup messages were in this file (which is why I
>> assumed it was the correct one), but for some reason after a
>> restart the logs were created as
>>
>> /var/log/postgresql/postgresql-8.3-main.log.1241706461
[...]
> is done in the zone spec
On Thursday 07 May 2009 7:42:40 am Conrad Lender wrote:
> On 07/05/09 15:58, Tom Lane wrote:
> > What seems most likely is that you're looking at the wrong log file.
> > Recheck the "where to log" settings.
>
> Thanks, Adrian and Tom,
>
> you were right, I wasn't looking at the correct file.
> My p
On 07/05/09 15:58, Tom Lane wrote:
> What seems most likely is that you're looking at the wrong log file.
> Recheck the "where to log" settings.
Thanks, Adrian and Tom,
you were right, I wasn't looking at the correct file.
My postgresql.conf has:
log_directory = '/var/log/postgresql'
log_filenam
Conrad Lender writes:
> SHOW log_min_messages;
> log_min_messages
> --
> notice
> (1 row)
> I thought this would cause all warnings to be logged automatically.
Yup.
> When
> I enter "COMMIT" in psql, I do get the warning, but I don't see it in
> the log file. What could be the
On Thursday 07 May 2009 3:33:09 am Conrad Lender wrote:
> Hello.
>
> We've recently discovered a bug in our code that resulted in COMMITs
> without BEGINs, and our client saw "no transaction in progress" warnings
> in his log file. What worries me is that we didn't discover this problem
> during de
10 matches
Mail list logo
