Hello,
I'm running a search query on a table with
approximately 120.000 rows
(3848 relpages, dbsize tablesize 30MB).
Because of poor performance I would like to cache
the complete table in memory, but I'm not sure which
config param I have
to use to accomplish
that.
The other tables
I am trying to replicate the DB
using pg_dump and pg_restore.When I use pg_restore it is appending the data to existing
data.This is not what I wanted.Even I used the flag -c .Can anybody throw
light on this.
On Thu, 28 Oct 2004, Andrei Bintintan wrote:
I try to dump a database from a 7.4.2 postgre system and to import it on
a 7.3.2. system, but I have a problem with the sequences in the dump.
In general, the above is not guaranteed to work. pg_dump will use features
of the dumping version so
Please see the FAQ at http://pginstaller.projects.postgresql.org/,
specifically question 3.2.
//Magnus
From: Wim Audenaert
[mailto:[EMAIL PROTECTED] Sent: Thursday, October
28, 2004 11:33 AMTo: [EMAIL PROTECTED]Subject:
[ADMIN] PostgreSQL on Windows - Connection problem
Can we call a java program in a
trigger .If so please let me know how to do that.
Thx
Hallo
I dumped a database with large objects with the command pg_dump -Fc -b
dbname dbname.dmp
To restore the DB I use pg_restore -d newdb dbname.dmp.
The restore process breakes with the following error message:
pg_restore: [archiver (db)] could not execute query: ERROR: relation
tablename
Hi,
One of our customers complains about
pg_ctl stop -m fast
could not shutdown PG server though we cannot reproduce the
same problem here.
They claim only -m immediate can take PG down
after 10 minutes of issuing -m fast.
The PG version is 7.3.2.
What might prevent -m fast
Okay, If I modify all the Sequences in the dump, everything works fine.
Is there any possibility to specify to the pg_dump to save the sequences
with the old type??? I mean not with No MAXVALUE and No Minvalue???
My problem is that the 7.3 database I cannot update it for the moment for
diverse
Lee Wu [EMAIL PROTECTED] writes:
They claim only -m immediate can take PG down after 10 minutes of
issuing -m fast.
The PG version is 7.3.2.
This is a known bug in 7.3.2 and before, if there is an idle backend
that hasn't received any user query since it got a SIGUSR2 interrupt.
2003-02-17
Title: RE: [ADMIN] pg_ctl stop -m fast
I've seen this happen. I think it happens because we have a Postgres database that is serving multiple webservers getting a high level of traffic. If you try to shut down the database while the webservers are still initiating connections to it, pg_ctl
10 matches
Mail list logo
