Hello,
I have a few queries regarding logging in Posgtresql 8.1 on windows:
1) Is the -l filename option same as using the log_directory and
log_filename attributes in postgresql.conf (assuming redirect_stderr is
on).
2) Is it ok to not see the -l filename details in the properties of
2007. május 17. 13.12 dátummal Khan, Mahmood Ahram ezt írta:
And my archive_command looks like this ( archive_command copy
c:\Program Files\PostgreSQL\8.2\data\pg_xlog d:\archive\ )
But it is loading the files in pg_xlogs folder itself. So Can
anybody have idea about this.
Did you
Hi,
I recently came upon this error message on one of our 8.1.1 server :
FATAL: could not read statistics message: Connection refused
Any ideas on what could possibly be the cause of this ?
Some search on the lists shows a similar error :
FATAL: could not read statistics message: Resource
On Fri, May 18, 2007 at 11:10:21AM -0400, Tom Lane wrote:
That's because it is the same :-(. You forgot to install the debuggable
executable, or something like that.
Well, I did install it and I did restart postgresql. Then I don't know
any way forward. I have tried the same process on a new,
Johann Spies [EMAIL PROTECTED] writes:
On Fri, May 18, 2007 at 11:10:21AM -0400, Tom Lane wrote:
That's because it is the same :-(. You forgot to install the debuggable
executable, or something like that.
Well, I did install it and I did restart postgresql. Then I don't know
any way
Am Montag, 21. Mai 2007 15:38 schrieb Peter Elmers:
I have searched the web and am sorry to say that i found nothing
about the default behavior of the log files of postgres.
That's easy: By default, postgres doesn't write a log file.
There are about half a dozen ways to set this up, though.
[EMAIL PROTECTED] (Peter Elmers) writes:
I have searched the web and am sorry to say that i found nothing
about the default behavior of the log files of postgres.
Can anyone tell me when postgres will delete the logfiles or what
postgres automatically do with them?
Can you be a bit more
Hi all, I'm having some trouble restarting a long-running server. Basically,
pg_ctl can't kill any processes waiting on a notify interrupt. Here's what
happened after trying a stop -m fast
[EMAIL PROTECTED] ~]# ps axvw | grep post
3606 ?S 3:30 23 3260 41575 6644 0.1
Peter Koczan [EMAIL PROTECTED] writes:
[ lots of processes stuck in notify interrupt code ]
That's weird. If it's still in that state, or if you can reproduce it,
could you attach to a few of those processes with gdb and get stack
traces?
Looking at the async.c code, an obvious candidate is
Hi,
now this might be a bit of a silly question, but I'll give it a shot anyway.
I'm working on a remote database for a few employees of a rather small
startup company where at least a few will get teleworking jobs. They'll
get a ms-access application that connects via ODBC from their home.
Hi Ray,
Sorry for late reply. Yes, I have tested your instructions and working
well. The think is now I need to configure so that it will always
automically start with the new location.
Thank you very much for the detailed instructions, really appreciated it.
Regards,
Dino
On 5/14/07, Ray
Each time you start postgres server using pg_ctl you have to mention the
data directory location using -D option. Alternatively you can specify in
the data_directory parameter of postgresql.conf file.
- vishal
From: Linux Geeks [EMAIL PROTECTED]
To: Ray Stell [EMAIL PROTECTED]
CC:
12 matches
Mail list logo