Re: [PERFORM] [BUGS] BUG #2567: High IOWAIT

2006-08-11 Thread Markus Schaber
Hi, Jim,

Jim Nasby wrote:

 Your biggest win would be to batch those inserts together into
 transactions, if possible.

Using COPY instead of INSERT might even give better wins, and AFAIK some
client libs use COPY internally (e. G. tablewriter from libpqxx).

 If not, the commit_delay settings might help you out.

As far as I understand, this will only help for concurrent inserts by
different clients, dealing throughput for latency. Please correct me if
I'm wrong.

HTH,
Markus
-- 
Markus Schaber | Logical TrackingTracing International AG
Dipl. Inf. | Software Development GIS

Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


Re: [PERFORM] Migrating data from DB2 to SQL Server

2006-08-11 Thread Markus Schaber
Hi, Eldhose,

contact1981 wrote:

 I am trying to migrate data from a DB2 database to SQL Server 2005
 database.  Does anyone know about any migration tool that does that?  I
 have heard about DB2 Migration Tool kit, but I think you can only
 migrate data to a DB2 database with that.  Thank you.

It seems that you, by accident, hit the wrong list with your question.

But, as you're here, why don't you migrate to PostgreSQL instead?


Have a nice day,
Markus

-- 
Markus Schaber | Logical TrackingTracing International AG
Dipl. Inf. | Software Development GIS

Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [PERFORM] Slow access to PostgreSQL server

2006-08-11 Thread Thomas Pundt
Hi,

On Thursday 10 August 2006 12:00, Phil Cairns wrote:
| In fact, the information is going from the
| server to the client machine at dialup speeds over a 100 Mb LAN to some
| machines, and full speed to others.
[...]
| There are no problems with copying files across the network.

and you are really really sure that this is not a network issue? I'd
double check that this is not a duplex mismatch, misconfigured router
or switch or something in that direction.

Ciao,
Thomas

-- 
Thomas Pundt [EMAIL PROTECTED]  http://rp-online.de/ 

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [PERFORM] setting up foreign keys

2006-08-11 Thread Sue Fitt
Solved, it turned out to be a lock caused by a gui connected to the 
database, even though the gui wasn't actually doing anything at the time...


Sue

Stephan Szabo wrote:

On Thu, 10 Aug 2006, Sue Fitt wrote:

  

Hi all,

This is my first post to the performance list, I hope someone can help me.

I'm setting up a table with 2 columns, both of which reference a column
in another table:

CREATE TABLE headwords_core_lexemes (
core_id int REFERENCES headwords_core(core_id),
lexeme_id int REFERENCES headwords_core(core_id),
);

Trouble is, it's taken 18 hours and counting!



What precisely is taking the time, the create table itself? The only thing
that the create should be waiting for as far as I know is a lock on
headwords_core to add the triggers.

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match

  


---(end of broadcast)---
TIP 4: Have you searched our list archives?

  http://archives.postgresql.org


Re: [PERFORM] setting up foreign keys

2006-08-11 Thread Spiegelberg, Greg
Sort of on topic, how many foreign keys in a single table is good v.
bad?  I realize it's relative to the tables the FK's reference so here's
an example:

Table A: 300 rows
Table B: 15,000,000 rows
Table C: 100,000 rows
Table E: 38 rows
Table F: 9 rows
Table G: is partitioned on the FK from Table A and has a FK column for
each of the above tables

I'm in the process of normalizing the database and have a schema like
this in mind.  Works wonderfully for SELECT's but haven't gotten the
data import process down just yet so I haven't had a chance to put it
through it's paces.  Depending on the performance of INSERT, UPDATE, and
COPY I may drop the FK constraints since my app could enforce the FK
checks.

TIA.

Greg
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Chris
 Sent: Thursday, August 10, 2006 6:36 PM
 To: Merlin Moncure
 Cc: Sue Fitt; pgsql-performance@postgresql.org
 Subject: Re: [PERFORM] setting up foreign keys
 
 Merlin Moncure wrote:
  On 8/10/06, Chris [EMAIL PROTECTED] wrote:
  Sue Fitt wrote:
   Thanks Chris and Chris, you've solved it.
  
   I had a gui open that connects to the database. It was doing 
   nothing (and not preventing me adding to or altering 
 headwords_core 
   via psql), but having closed it the table is instantly 
 created. Weird.
  
   BTW, referencing the same column twice is deliberate, it's a 
   cross-reference.
 
  The same column and the same table?
 
  Same column different table I could understand but not the same 
  column  table ;)
  
  create table color(color text);
  
  create table person(eye_color text references color(color), 
 hair_color 
  text references color(color));
 
 lol. Good point :)
 
 *back to the hidey hole!*
 
 --
 Postgresql  php tutorials
 http://www.designmagick.com/
 
 ---(end of 
 broadcast)---
 TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] 
 so that your
message can get through to the mailing list cleanly
 

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster