Re: PHP SQL - Mailing list pgsql-general

From Shaun Clements
Subject Re: PHP SQL
Date
Msg-id 100F78F2B203444BB161BBA7077FF6131CD968@srldbexc003.relyant.co.za
Whole thread Raw
In response to PHP SQL  (Shaun Clements <ShaunC@relyant.co.za>)
List pgsql-general

Thanks for your response.
It is as you mentioned, within the same database.
I will get working on a stored procedure this morning.

Thanks for your response.

Kind Regards,
Shaun Clements

-----Original Message-----
From: Jeff Davis [mailto:jdavis-pgsql@empires.org]
Sent: 22 March 2005 10:48 PM
To: Shaun Clements
Cc: PgSQL General List
Subject: Re: [GENERAL] PHP SQL

> pg_fetch_row
> pg_fetch_assoc
> pg_fetch_object
> pg_fetch_result
> pg_fetch_array
>
> Are there performance differences, which are noticeable?

I doubt you'll see much real difference. Your real bottleneck will be
I/O.

You might be able to save something by using COPY out and then back in.
If it's a lot of data I would definately try that, because it's got a
lot more chance of helping you. Or you could use a server side function
rather than doing the work in the client. contrib/dblink may be able to
help you a lot.

However, your question made it sound like the tables were in the same DB
already and just in different schemas? If that's the case, you can just
select one table into another and avoid all that unecessary overhead.

Regards,
        Jeff Davis

pgsql-general by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: inherited table and rules
Next
From: "Sim Zacks"
Date:
Subject: Re: multi line text data/query ?bug?