Bernd Nawothnig writes:
> A client application written in C# + npgsql 2.0.6 causes reproducable
> log entries like this:
> LOG: unexpected EOF on client connection
> LOG: could not receive data from client: Die Verbindung wurde vom
> Kommunikationspartner zurückgesetzt(*)
This just indicates
Hello,
A client application written in C# + npgsql 2.0.6 causes reproducable
log entries like this:
LOG: unexpected EOF on client connection
LOG: could not receive data from client: Die Verbindung wurde vom
Kommunikationspartner zurückgesetzt(*)
(*) Connection reset by peer
The responsable Pr
<[EMAIL PROTECTED]> writes:
> FATAL: sorry, too many clients already
You need a larger max_connections setting.
> LOG: unexpected EOF on client connection
I think pgbench just dies ungracefully if it gets a connection failure.
regards, tom lane
---
Hi list,
I am doing a benchmark in my database but it is spent too much time.
I was looking for my log file but I could not understad clearly what it says.
The log is like this:
INT: Consider increasing the configuration parameter "checkpoint_segments".
LOG: checkpoints are occurring too fre
Gerardo Herzig <[EMAIL PROTECTED]> writes:
> Hi dudes. I have my pg log file rotation configured so i have a
> psql_`today`.log. The thing is, can i configure postgres so the file
> permissions (today is 600) could by 640, so developers could login and
> tailf the logfile (without using the post
Gerardo Herzig wrote:
> Hi dudes. I have my pg log file rotation configured so i have a
> psql_`today`.log. The thing is, can i configure postgres so the file
> permissions (today is 600) could by 640, so developers could login and
> tailf the logfile (without using the postgres superuser, course)?
Hi dudes. I have my pg log file rotation configured so i have a
psql_`today`.log. The thing is, can i configure postgres so the file
permissions (today is 600) could by 640, so developers could login and
tailf the logfile (without using the postgres superuser, course)?
Thanks!
Gerardo
--
Thank you Shoiab,
Now everything is working like I desire. Thank you all very much.
I am notthing without Postgresql community.
Ezequias
2007/1/31, Shoaib Mir <[EMAIL PROTECTED]>:
No problemo :)
What was the query and the statement for error? that way we might be able
to help...
--
No problemo :)
What was the query and the statement for error? that way we might be able to
help...
-
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 1/31/07, Ezequias Rodrigues da Rocha <[EMAIL PROTECTED]> wrote:
Great. Now the log is working. Thank you, Thank you, Thank you,
Great. Now the log is working. Thank you, Thank you, Thank you,
But my statement does not report an error anymore. I really confused now.
Any suggestion ?
Ezequias
2007/1/31, Shoaib Mir <[EMAIL PROTECTED]>:
You need to set it like this:
log_destination = 'syslog,stderr'
redirect_stderr = on
On Wed, 2007-01-31 at 10:12 -0200, Ezequias Rodrigues da Rocha wrote:
> I restart the server but the pg_log folder doesn't appears.
>
> My log session is like this on postgresql.conf:
>
> # These are only used if redirect_stderr is on:
Did you look
You need to set it like this:
log_destination = 'syslog,stderr'
redirect_stderr = on
and then restart the server. It should show up the log from then onwards
---
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 1/31/07, Ezequias Rodrigues da Rocha <[EMAIL PROTECTED]> wrote:
I really don't know how to set it. I created my pg_log on:
/var/lib/pgsql/data.
the settings on pgsql.conf is like this:
#---
# ERROR REPORTING AND LOGGING
#---
I did it, my pg_log folder was like this:
drwxr-xr-x 2 root root 4096 Jan 31 09:36 pg_log
Afer I changed to:
drwxr-xr-x 2 postgres postgres 4096 Jan 31 09:36 pg_log
After this I restart the service (service postgresql restart) ,return to
execute an inaceptble sql statement with t
You need to create the folder manually, give the postgres user permission
for write on it and then restart the database server. This way you should be
able to set the log files in pg_log folder...
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 1/31/07, Ezequias Rodrigues da Rocha
Change it in the postgresql.conf file only if you want to make it permanent.
Otherwise just set the variable for your current session without a
server restart.
--Imad
www.EnterpriseDB.com
On 1/31/07, Ezequias Rodrigues da Rocha <[EMAIL PROTECTED]> wrote:
It was commented. Thank you Shoaib Mir
I restart the server but the pg_log folder doesn't appears.
My log session is like this on postgresql.conf:
# These are only used if redirect_stderr is on:
log_directory = 'pg_log'# Directory where log files are written
# Can be absolute or relative to PGDATA
log_filen
It was commented. Thank you Shoaib Mir
I must restart my server ?
Ezequias
2007/1/31, Shoaib Mir <[EMAIL PROTECTED]>:
Check for log_directory setting in your postgresql.conf file...
-
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 1/31/07, Ezequias Rodrigues da Rocha <[EMAIL
Check for log_directory setting in your postgresql.conf file...
-
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 1/31/07, Ezequias Rodrigues da Rocha <[EMAIL PROTECTED]> wrote:
I noticed today morning that my pg.log doesn't exist in my server.
Why it occurs ?
My /var/lib/pgsql
I noticed today morning that my pg.log doesn't exist in my server.
Why it occurs ?
My /var/lib/pgsql/data is like that:
[EMAIL PROTECTED] data]# ls -la
total 92
drwx-- 10 postgres postgres 4096 Jan 31 08:35 .
drwx-- 4 postgres postgres 4096 Jul 26 2006 ..
drwx-- 7 postgres p
On Tue, Jan 30, 2007 at 04:41:13PM -0200, Ezequias Rodrigues da Rocha wrote:
> So you are tell me that it is impossible to retrieve it ok ?
No.
> Just by changing this values (what I did now) it is possible to get
> the error messages and their statements OK?.
Yes, but you need to signal the po
So you are tell me that it is impossible to retrieve it ok ?
Just by changing this values (what I did now) it is possible to get
the error messages and their statements OK?.
My best Regards
Ezequias
2007/1/30, Andrew Sullivan <[EMAIL PROTECTED]>:
On Tue, Jan 30, 2007 at 03:01:05PM -0200, Ezequ
On Tue, Jan 30, 2007 at 03:01:05PM -0200, Ezequias Rodrigues da Rocha wrote:
> I know there are many logs in postgresql but I don't have many
> familiarity with all them.
It's not totally plain what you want to have happen -- whether you
want all queries, whether you merely want ERRORs to show up
Hi list,
I lost some data becouse my application does not throws an exception
when an update statement report an error.
It is possible to find out if the PostgreSQL could have this error
(and more important the complete statement that make this errors
occurs) ?
I know there are many logs in pos
Bryce Nesbitt <[EMAIL PROTECTED]> writes:
> My postmaster won't start. This is on a Fedora Core fc5 box, new and clean.
> It's postgres 8.1.4. All I get is "LOG: logger shutting down" in the
> pgstartup.log.
My first instinct is to think selinux issue. Are you up2date on selinux
policy patches
My postmaster won't start. This is on a Fedora Core fc5 box, new and clean.
It's postgres 8.1.4. All I get is "LOG: logger shutting down" in the
pgstartup.log.
I've checked for permission errors.
At the relevant moment I get:
# sh -x /etc/init.d/postgresql start
...
++ cat /var/lib/pgsql/data/
Hello,
i have installed the 8.0 beta3-dev1 version of
postgres on my pc, and I want to disable log. How can I do? It is possible to
disable and don’t write all the log, or how can I write all the log in a
specific directory??
Thanks
Negri Davide
---
Outgoing mail is certif
27 matches
Mail list logo
