Hi Theo,
yes you can log every SQL statement.
Just edit the postgresql.conf and delete the remark (#) from the following line:
#log_statement = false
Then restart postgres.
After this you can find every statement in the postgresql.log. On Gentoo you can
find this log in /var/lib/postgresql/data.
Title: Postgres SQL Monitor tool
Is there a log file, or a method of logging all the SQL statements a postgres server processes. I can look at pg_stat_activity which tells me each postgres process and the current query running, however I wanted to see a log file, similar to SQL Servers Profile
Take a look at OSDL. PostgreSQL is their default database test
platform.
http://www.osdl.org/ or, more specifically, the dbt test suite site:
http://sourceforge.net/projects/osdldbt/
On Tue, 2004-09-21 at 21:11, Cao Van Khanh wrote:
> My work is making PostgreSQL run as fast as posible , but th
My work is making PostgreSQL run as fast as posible , but
there’re a lot of parameter . So I would like to have your help . When I
change some parameter , I can not find out is better or not . I need some tool
to test the perfomence of postgeSQL . Anyone could help me ?
I have to configure PostgreSQL 7.4.5 for my company , and
with the Run-time Configuration , I think some think there can help me to
improve perfoment of the database server .
But without any experience , I deeply need help from you ! My
system is Pentium4 , 2,4Gz CPU and 1Gbs of RAM . I
On Tuesday 21 September 2004 07:59, Magnus Hagander wrote:
> > > I guess another alternative is jut remove faq_mswin from the main
> > > sources and then leave it up to cygwin/native projects to maintain
> > > thier own faqs, with perhaps a single question in the main
> >
> > postgresql
> >
> > > p
"Olivier Hubaut" <[EMAIL PROTECTED]> writes:
> I used to make synchrnoistation between data directories with Rsync cause
> it's faster when synchronizing offline database than making a dump.
This has never been considered a supported technique. You can usually
get away with it if the source and
"Pradeepkumar, Pyatalo (IE10)" <[EMAIL PROTECTED]> writes:
> I get the following error.
> createuser: could not connect to database template1: FATAL: could not open
> file "/usr/local/pgsql/data/global/1262": Permission denied
Looks like you started the postmaster as the wrong user (ie, not t
Hi,
I used to make synchrnoistation between data directories with Rsync cause
it's faster when synchronizing offline database than making a dump.
It works really nice between all the PowerPC we used, but it doesn't work
on x86 server (the postmaster refuses to start because the
PG_CONTROL_VE
Hi all,
I was just trying to add some users to my databasei followed the
createuser help and gave the following command
[root]#/usr/local/pgsql/bin/createuser -ADe epsadmin
I get the following error.
createuser: could not connect to database template1: FATAL: could not open
file "
> > I guess another alternative is jut remove faq_mswin from the main
> > sources and then leave it up to cygwin/native projects to maintain
> > thier own faqs, with perhaps a single question in the main
> postgresql
> > pointing to both of the other faqs... anyone have a preference?
>
> The p
> -Original Message-
> From: Robert Treat [mailto:[EMAIL PROTECTED]
> Sent: 21 September 2004 12:27
> To: Magnus Hagander
> Cc: Bender, Cheryl; [EMAIL PROTECTED]; Dave Page;
> [EMAIL PROTECTED]
> Subject: Re: [ADMIN] windows docs?
>
?
> I'm thinking rename the current faq to faq_win32
On Tuesday 21 September 2004 04:35, Magnus Hagander wrote:
> > > When starting the Windows psql client I get a warning that the
> > > "console codepage (437) differs from the windows codepage
> >
> > (1252)" and
> >
> > > to see installation on Windows for details. I am having
> >
> > trouble find
> > When starting the Windows psql client I get a warning that the
> > "console codepage (437) differs from the windows codepage
> (1252)" and
> > to see installation on Windows for details. I am having
> trouble finding this
> > documentation. I've also been looking for the "Windows
> FAQ"
Hye
I had a similar problem and I solved it by :
* deleting and re-creating the user with passwd
* Verify in pg_hba.conf the access and users (It is at this level I had
problem from fields -be carefull with the editor- and the "identuser" /
try to put trust in a first time)
* giving rights to t
15 matches
Mail list logo