Hi,
--- a little off topic ---
I want to do something so informative like the map that was in the
prev main developer page.
Can anyone point me about what tool to use? and maybe some guidance on this?
thanks,
Jaime Casanova
---(end of broadcast)-
Hi!
Bruce Momjian [2005-02-09 18:05 -0500]:
> > However, I just stumbled across another problem: libpq3 and the new
> > libpq4 use the same translation domain "libpq4", thus they cannot be
> > installed in parallel. Can you please change the domain to "libpq4" as
> > well? This should generally be
On Thu, 2005-02-10 at 14:37 -0500, Bruce Momjian wrote:
> No, we feel that is of limited value. If the optimizer isn't doing
> things properly, we will fix it.
I agree that improving the optimizer is the right answer for normal
usage, so I can't get excited about query-level plan hints, but I can
Hicham
For your experiments (VLDB ? :-) your best bet of specifically bolting
on a plan (if you can't convince the optimizer to do the right thing)
is to hack it in the query planner.
I've done similar hacks in the past, but only in the TelegraphCQ code
and not in PostgreSQL.
--
Pip-pip
Sail
Hicham G. Elmongui wrote:
> Is there a way to bypass the optimizer and to specify a plan to be executed?
>
> Something like:
>
>
>
> Limit
> -> Nested Loop
> -> Nested Loop
> -> Seq Scan on tab00 t00
> -> Index Scan using tab03_pkey on tab03 t03
> I
Is there a way to bypass the optimizer and to specify a plan to be executed?
Something like:
Limit
-> Nested Loop
-> Nested Loop
-> Seq Scan on tab00 t00
-> Index Scan using tab03_pkey on tab03 t03
Index Cond: ("outer".id = t03.id)
-> Index Sca
> Lately, I have been thinking that a cool form of index would be some
sort
> of "persistent reference" index. Like the old ISAM days of yore, a
fixed
> number could point you right to the row that you want. I'm not sure if
the
> "persistent reference" is a specific auto numbering column type or
>
> If that ID is the only thing you use to access that data, why not just
> store
> it in a flat file with fixed-length records? seek() (or your language's
> equivalent) is usually fast.
As a matter of policy, I would never manage data outside of the database.
>
> If you need to drive that from wi
Title: RE: [HACKERS] New form of index "persistent reference"
If that ID is the only thing you use to access that data, why not just store it in a flat file with fixed-length records? seek() (or your language's equivalent) is usually fast.
If you need to drive that from within PostgreSQL, yo
Martin Pitt wrote:
-- Start of PGP signed section.
> Hi!
>
> Bruce Momjian [2005-02-09 18:05 -0500]:
> > > However, I just stumbled across another problem: libpq3 and the new
> > > libpq4 use the same translation domain "libpq4", thus they cannot be
> > > installed in parallel. Can you please chan
> Pavel Stehule <[EMAIL PROTECTED]> writes:
> > Can you help me other possibilities?
>
> Create the temp table only once per connection (you can use ON COMMIT
> DELETE ROWS instead of ON COMMIT DROP to clean it out). Then you won't
> need to use EXECUTE.
>
I am not sure so it's possible. I use p
For about 5 years now, I have been using a text search engine that I wrote
and maintain.
In the beginning, I hacked up function mechanisms to return multiple value
sets and columns. Then PostgreSQL aded "setof" and it is was cool. Then it
was able to return a set of rows, which was even better.
L
Pavel Stehule <[EMAIL PROTECTED]> writes:
> Can you help me other possibilities?
Create the temp table only once per connection (you can use ON COMMIT
DELETE ROWS instead of ON COMMIT DROP to clean it out). Then you won't
need to use EXECUTE.
regards, tom lane
--
Dave Page wrote:
-Original Message-
From: [EMAIL PROTECTED] on behalf of Michael Fuhr
Sent: Wed 2/9/2005 4:22 AM
To: Premsun Choltanwanich
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] How can I use large object on PostgreSQL Linux
I wonder if admin is pgadmin-tools.
Yes, it
How to write a rule to avoid queries like update,insert,delete,select
from any database users except superuser.
REVOKE UPDATE,INSERT,DELETE,SELECT ON table FROM PUBLIC, other users;
Chris
---(end of broadcast)---
TIP 9: the planner will ignore your
How to write a rule to avoid queries like update,insert,delete,select from any database users except superuser.
thanks,
Prashant
Do you Yahoo!?
Yahoo! Search presents - Jib Jab's 'Second Term'
16 matches
Mail list logo