Re: [SQL] [GENERAL] Postgresql slow on XEON 2.4ghz/1gb ram
If you went from a dual processor box running windows to a single
processor box running windows, I wouldn't be surprised to see a slow
down. I'd recommend switching from Windows to Linux/BSD over a hardware
upgrade any day.
Robert Treat
On Wed, 2003-08-06 at 18:04, Maksim Likharev wrote:
> What OS, if Linux what kernel
>
> -Original Message-
> From: Wilson A. Galafassi Jr. [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 06, 2003 6:51 AM
> To: [EMAIL PROTECTED]
> Subject: [GENERAL] Postgresql slow on XEON 2.4ghz/1gb ram
>
>
>
> Hello.
> I have this problem: i'm running the postgre 7.3 on a windows 2000
> server with P3 1GHZ DUAL/1gb ram with good performance. For best
> performance i have change the server for a XEON 2.4/1gb ram and for my
> suprise the performance decrease 80%. anybody have a similar experience?
> does exist any special configuration to postgre running on a Xeon
> processor? Any have any idea to help-me? Excuse-me my bad english.
> Very Thanks
> Wilson
> icq 77032308
> msn [EMAIL PROTECTED]
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 8: explain analyze is your friend
Re: [SQL] Analyze makes queries slow...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 06 August 2003 08:18, Stef wrote: > > Can anybody help, or give some links to good > help resources? > Try the performance list. Attach the create statements used to create the tables, the query you are running, and the different explain plans that were generated. If you know what it is, you may also want to attach the relevant statistics from the pg_stats table. They will be most helpful. - -- Jonathan Gardner <[EMAIL PROTECTED]> Live Free, Use Linux! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/M87QWgwF3QvpWNwRAgMfAJ9c6O9EyVbJYiguv/b2wtf/NsLZfACgq3lW YjpMSEMZ4gfyGaGoJcOjpSo= =4/hA -END PGP SIGNATURE- ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[SQL] unexpected chunk value
hello all When i tried ´pg_dump -v -f dump.dmp dtbtransporte´ I got the error: pg_dump: restoring data for table tbdmovimento pg_dump: dumping out the contents of table tbdmovimento pg_dump: ERROR: unexpected chunk number 8 (expected 0) for toast value 6935693 pg_dump: lost synchronization with server, resetting connection pg_dump: SQL command to dump the contents of table "tbdmovimento" failed: PQendcopy() failed. pg_dump: Error message from server: pg_dump: The command was: COPY "tbdmovimento" TO stdout; pg_dump: *** aborted because of error So I´ve ran a query to see which pg_toast from this tbdmovimento So I shutdown de postmaster and up a standalone backend and reindexed the database (REINDEX DATABASE dtbtransporte FORCE). All this after a vacuum analyze. How the pg_dump still returns above error, I´ve tried to REINDEX the index pg_toast_16557. Reindex ran ok, but the pg_dump still returns this error. any ideas. tnx Eric
[SQL] Books in french
For all french people in this list : I search books about postgresql in French with explanations of tree structure functions, optimisation of install not novice books Thx a lot ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[SQL] Using rowtype as function argument
Hi all, I suppose this must be easy to figure out, but I can't find it anywhere in the documentation. How do I call a function that takes a rowtype for an argument as in: CREATE FUNCTION myfunc(mytablename) RETURNS INT AS ' BEGIN -- Do stuff RETURN val; END; ' LANGUAGE 'plpgsql' How do I call this function? I haven't been able to figure it out or find it anywhere... Thanks in advance, Martin ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[SQL] [pg-sql] - Problem with duplicate table (PostgreSQL 7.2.3
I have to duplicate a table to save different instances of datas.
Structure de la table "spectacle"
*/
CREATE TABLE "spectacle" (
id_spectacle SERIAL,
"id_membre_adherent" INTEGER NOT NULL,
"id_genre_festival" INTEGER,
"id_festival" INTEGER,
"nom" VARCHAR(255),
"compagnie_interprete" VARCHAR(255),
"vitaculture" INTEGER NOT NULL,
"regionales" INTEGER NOT NULL,
"presentation" TEXT,
"genre_precision" VARCHAR(255),
"duree" VARCHAR(255),
"photo1" VARCHAR(255),
"photo1_credit" VARCHAR(255),
"photo2" VARCHAR(255),
"photo2_credit" VARCHAR(255),
"salle" TEXT,
"tarifs" TEXT,
"id_traitement" INTEGER DEFAULT 1,
"distribution" TEXT,
"type_public" VARCHAR(255),
PRIMARY KEY("id_spectacle"),
FOREIGN KEY ("id_festival") REFERENCES "festival"("id_festival")
ON DELETE RESTRICT
ON UPDATE RESTRICT
NOT DEFERRABLE,
FOREIGN KEY ("id_genre_festival") REFERENCES
"genre_festival"("id_genre_festival")
ON DELETE RESTRICT
ON UPDATE RESTRICT
NOT DEFERRABLE,
FOREIGN KEY ("id_membre_adherent") REFERENCES
"membre_adherent"("id_membre_adherent")
ON DELETE CASCADE
ON UPDATE RESTRICT
NOT DEFERRABLE,
FOREIGN KEY ("id_traitement") REFERENCES "traitement"("id_traitement")
ON DELETE RESTRICT
ON UPDATE RESTRICT
NOT DEFERRABLE
) WITH OIDS;
CREATE INDEX "adherant_spectacle_fk" ON "spectacle"
USING btree ("id_membre_adherent");
CREATE INDEX "genre_spectacle_fk" ON "spectacle"
USING btree ("id_genre_festival");
CREATE INDEX "spectacle_au_festival_fk" ON "spectacle"
USING btree ("id_festival");
When I duplicate this code in an other table named spectacle_v without
Foreygn key ... all is running.
But when I try to delete a spectacle_membre, linked value in spectacle
are correctly deleted, but I have an error for spectacle_v which is not
linked :
(ERROR: referential integrity violation - key in membre_adherent still
referenced from spectacle_v )
I do not understand this message error, because any foreign key is
referenced with this table.
---(end of broadcast)---
TIP 8: explain analyze is your friend
Re: [SQL] Abort Transaction DP PK (again)
Alexandre, > It´s very difficult to change the behaviour of a duplicate PK, from > "error" to "warning"? That would be a very bad idea because then the duplicate row would be inserted anyway. And you'd have to hack the source code. > It´s possible, in a future release, to have an exception-handling for all > client interfaces, like ODBC or JDBC? I'm not quite sure what you mean. -- -Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
