I tried posting this before, but I don't think it got posted. Sorry if
it did.
According to the Wikipedia article on PostgreSQL
(http://en.wikipedia.org/wiki/PostgreSQL), it has a feature for
automatic joins:
"SELECT u.* FROM user u, address a WHERE a.city='New York' and
a.user_name=u.user_name
I
According to the Wikipedia article on PostgreSQL
(http://en.wikipedia.org/wiki/PostgreSQL), it has a feature for
automatic joins:
"SELECT u.* FROM user u, address a WHERE a.city='New York' and
a.user_name=u.user_name
In Postgres the relationship between users and addresses can be
explicity de
Mike Mascari <[EMAIL PROTECTED]> writes:
> as you can see, over ten runs for each category, GEQO loses big. I get
> (in seconds):
> label | count | avg | stddev
> -+---++-
> NO GEQO PLAN|10 | 0.8809 | 0.0056460408
Tom Lane wrote:
Mike Mascari <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Uh ... dare I ask whether you think it's too high? Or too low?
Too low. In fact, after testing some of my queries which are a bit large
(# of tables) in size, I usually just wind up turning it off.
Well
Quoting Leif K-Brooks <[EMAIL PROTECTED]>:
> I've been programming web applications in PHP/MySQL for a few years.
> It's worked pretty well, but I've been getting annoyed with the lack of
> more advanced features lately. After some reading, I've decided to
> switch to Perl/PostgreSQL.
>
> I'll
Shridhar Daithankar <[EMAIL PROTECTED]> writes:
> http://developer.postgresql.org/docs/postgres/tutorial.html
> Just remember, this is a developer version of documentation and subject to
> change. Better stick to local documentation of a released version
You should really only use the above link
Mike Mascari <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Uh ... dare I ask whether you think it's too high? Or too low?
>>
> Too low. In fact, after testing some of my queries which are a bit large
> (# of tables) in size, I usually just wind up turning it off.
Well, that's why it's config
You should look into the tutorial.
http://developer.postgresql.org/docs/postgres/tutorial.html
Look for postgresql documentation in your install. It should have it as well.
Also you could look at http://www.varlena.com which publishes mini
howtos based on discussions on this
list.
Also yo
Hello,
Well... 7.4 to 7.4.1 is a direct upgrade. You do not have to do a
reinitdb which means you do
not have to reconfigure the system. I can't help you with your BSD
specific issues (I don't know much about it)
but from the PostgreSQL perspective, you should be abble to just upgrade.
One n
unsubscribe
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
On Saturday 17 January 2004 16:19, Leif K-Brooks wrote:
> I've been programming web applications in PHP/MySQL for a few years.
> It's worked pretty well, but I've been getting annoyed with the lack of
> more advanced features lately. After some reading, I've decided to
> switch to Perl/PostgreSQL.
I've been programming web applications in PHP/MySQL for a few years.
It's worked pretty well, but I've been getting annoyed with the lack of
more advanced features lately. After some reading, I've decided to
switch to Perl/PostgreSQL.
I'll be discarding all database data for other reason anyway
Tom Lane wrote:
Mike Mascari <[EMAIL PROTECTED]> writes:
But just as a quick notice to those upgrading from 7.3 to 7.4 with fully
normalized databases requiring > 11 joins, the GEQO setting can be a
killer...
Uh ... dare I ask whether you think it's too high? Or too low?
Too low. In
13 matches
Mail list logo
