[EMAIL PROTECTED] (Jeff Boes) writes:
> (Environment: Pg 7.4.1 on Linux; yes, I know it's past time to
> upgrade.)
If you were running 7.2, I'd be pestering you ;-).
We didn't get rid of our last 7.1 system until last December, and I
think the backend is probably still running, albeit with nothin
Jeff Boes <[EMAIL PROTECTED]> writes:
> What would cause an otherwise well-behaved table to start doing this? Is
> this just a "dead spot" in the ANALYZE command? (By which I mean:
> ANALYZE randomly sampling rows, but my data is not terribly random, so
> it gets fooled?)
7.4's ANALYZE is indeed e
(Environment: Pg 7.4.1 on Linux; yes, I know it's past time to upgrade.)
(Originally, I started to post this as a question about how
pg_class.reltuples could get so far out of whack compared to the actual
table size. After posting it, I found that (a) I had the mailing list
address wrong [d'oh!]
Hi Anjan,
I used to follow this procedure while using Postgres 7.4 version, we
are now using Postgres 8.0.2 and I dont have give the log file path name
everytime I start the postgres , I use these paramaters in the
postgresql.conf
redirect_stderr = true
log_directory = '/var/lib/pgsql8/
Scott Marlowe wrote:
On Wed, 2005-05-18 at 09:49, Pallav Kalva wrote:
Scott Marlowe wrote:
On Wed, 2005-05-18 at 08:35, Pallav Kalva wrote:
Hi Everybody,
I am having problems with logging long running SQL in the log file.
I have set log_min_duration_statement = 5000 (5secs) and it
For logging the queries taking 5+ seconds, try this:
In postgresql.conf:
syslog = 0# range 0-2; 0=stdout; 1=both; 2=syslog
syslog_facility = 'LOCAL0'
syslog_ident = 'postgres'
log_min_duration_statement = 5000
Then, in your pg startup script (etc/init.d/Postgresql), you want to
have somethin
On Wed, 2005-05-18 at 09:49, Pallav Kalva wrote:
> Scott Marlowe wrote:
>
> >On Wed, 2005-05-18 at 08:35, Pallav Kalva wrote:
> >
> >
> >>Hi Everybody,
> >>
> >>
> >>I am having problems with logging long running SQL in the log file.
> >>I have set log_min_duration_statement = 5000 (5secs)
Pallav Kalva <[EMAIL PROTECTED]> writes:
>>> I am having problems with logging long running SQL in the log file.
>>> I have set log_min_duration_statement = 5000 (5secs) and it is not
>>> logging sql statements that took over 5 secs and this is only from
>>> queries generated by Hibernate .
The
Tom Lane wrote:
Pallav Kalva <[EMAIL PROTECTED]> writes:
I am having problems with logging long running SQL in the log file.
I have set log_min_duration_statement = 5000 (5secs) and it is not
logging sql statements that took over 5 secs and this is only from
queries generated by Hibernate
Pallav Kalva <[EMAIL PROTECTED]> writes:
> I am having problems with logging long running SQL in the log file.
> I have set log_min_duration_statement = 5000 (5secs) and it is not
> logging sql statements that took over 5 secs and this is only from
> queries generated by Hibernate .
Did you
Scott Marlowe wrote:
On Wed, 2005-05-18 at 08:35, Pallav Kalva wrote:
Hi Everybody,
I am having problems with logging long running SQL in the log file.
I have set log_min_duration_statement = 5000 (5secs) and it is not
logging sql statements that took over 5 secs and this is only from
quer
On Wed, 2005-05-18 at 08:35, Pallav Kalva wrote:
> Hi Everybody,
>
>
> I am having problems with logging long running SQL in the log file.
> I have set log_min_duration_statement = 5000 (5secs) and it is not
> logging sql statements that took over 5 secs and this is only from
> queries gen
The easiest way is to shut down both postmaters and do a plain copy of the
data cluster directories.
Another way (with doubling space) is to use pg_dumpall
|-Original Message-
|From: Ing. Jhon Carrillo [mailto:[EMAIL PROTECTED]
|Sent: Mittwoch, 18. Mai 2005 15:28
|To: pgsql-admin@postgresq
On Wed, 2005-05-18 at 08:27, Ing. Jhon Carrillo wrote:
> Hi all,
>
> I have two postgresql 7.4 (Linux) servers:
>
> Server A: it has a original database.
> Server B: it doesn't have nothing.
>
>
> I need to transfer the database/server A to database/server B through the
> some command directly
On May 18, 2005, at 9:27 AM, Ing. Jhon Carrillo wrote:
I need to transfer the database/server A to database/server B through
the
some command directly.
pg_dumpall might be what you are looking for.
http://www.postgresql.org/docs/8.0/interactive/app-pg-dumpall.html
John DeSoi, Ph.D.
http://pgedit
Hi all,
I have two postgresql 7.4 (Linux) servers:
Server A: it has a original database.
Server B: it doesn't have nothing.
I need to transfer the database/server A to database/server B through the
some command directly.
thanks.
Jhon Carrillo
Ingeniero en Computación
[EMAIL PROTECTED]
+58414
Hi Everybody,
I am having problems with logging long running SQL in the log file.
I have set log_min_duration_statement = 5000 (5secs) and it is not
logging sql statements that took over 5 secs and this is only from
queries generated by Hibernate . here is a sample query from hibernate :
---
17 matches
Mail list logo
