Possibly.
A lot of my queries show comparable performance, some a little slower
and a few a little faster. There are a few, however, that really grind on
PostgreSQL. I am leaning patterns from these to try and and target the
most likely performance problems to come and hand tune these types
Unfortunately I don't understand the question!
My background is the primarily Win32. The last time I used a *nix OS
was about 20 years ago apart from occasional dips into the linux OS
over the past few years. If you can tell be how to find out what you want
I will gladly give you the
Unfortunately I have to try and keep both SQLServer and PostgreSQL
compatibilty. Our main web application is currently SQLServer, but we
want to migrate customers who don't care what the DB server is over to
PostgreSQL. Some of our larger customers demand SQLServer, you
know how it is!
I
On 04/04/2004 09:56 Gary Doades wrote:
Unfortunately I don't understand the question!
My background is the primarily Win32. The last time I used a *nix OS
was about 20 years ago apart from occasional dips into the linux OS
over the past few years. If you can tell be how to find out what you want
Hi,
Try looking at the contrib/tablefunc add-in module.
Chris
Kamalraj Singh Madhan wrote:
Hi Friends,
Does anybody know the substitute of the oracle function 'connect by
prior' in postgre sql.
The query is basically being used to get a tree structure of records. The
query in oracle
On Sun, 2004-04-04 at 01:56, Gary Doades wrote:
Unfortunately I don't understand the question!
My background is the primarily Win32. The last time I used a *nix OS
was about 20 years ago apart from occasional dips into the linux OS
over the past few years. If you can tell be how to find
Hi Aaron,
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Aaron Werman
Sent: vrijdag 2 april 2004 13:57
another thing that I have all over the place is a hierarchy:
index on grandfather_table(grandfather)
index on father_table(grandfather,
On 3 Apr 2004 at 21:23, Mike Nolan wrote:
Almost any cross dbms migration shows a drop in performance. The engine
effectively trains developers and administrators in what works and what
doesn't. The initial migration thus compares a tuned to an untuned version.
I think it is also
