Gregory Stark [EMAIL PROTECTED] writes:
I think there's still a problem here with some kind of n^2 behaviour for
appends of very wide tables but I haven't quite nailed it yet. In any case is
there any reason not to make the following small change to move the constraint
exclusion ahead of the
Andrew Dunstan wrote:
Log Message:
---
Add --with-libxslt configure option
It should be added to the installation documentation as well.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: You
Neil Conway [EMAIL PROTECTED] writes:
On Fri, 2007-04-20 at 02:55 -0400, Tom Lane wrote:
I don't think you've thought of quite all of the failure cases. One
that's a bit pressing is that a deadlock isn't necessarily confined to
objects in your own database.
I'm not sure I follow. If we
Hi again
It seems now that I am one step away from the end. So far I have succeeded
in returing row by row from the backend to the frontend, knew this from
debugging.
Now comes the point of displaying them directly not to wait till the end of
the query. These are the steps I took:
1)
But then what about the null values? Perhaps unique + notnull is better?
Otto
2007/4/20, Nicolas Barbier [EMAIL PROTECTED]:
2007/4/16, Ottó Havasvölgyi [EMAIL PROTECTED]:
Eliminate the table T from the query/subquery if the following
requirements
are satisfied:
1. T is left joined
2. T
Hello
For a particular query, are there any functions which can give me the
start-up cost, total run-cost, number of rows and width?
Thanks,
Sharat.
I've been seeing this failure intermittently on Narwhal HEAD, and once
on 8.1. Other branches have been OK, as have other animals running on
the same physical box. Narwhal-HEAD is run more often than any other
builds however.
Anyone have any idea what might be wrong? It seems unlikely to be a
On Apr 21, 2007, at 4:46 , sharath kumar wrote:
For a particular query, are there any functions which can give me
the start-up cost, total run-cost, number of rows and width?
-hackers is a list for discussion of development of PostgreSQL
itself. Your question would probably be more
Peter Eisentraut wrote:
Andrew Dunstan wrote:
Log Message:
---
Add --with-libxslt configure option
It should be added to the installation documentation as well.
done
cheers
andrew
---(end of broadcast)---
TIP 3: Have
Tom Lane [EMAIL PROTECTED] writes:
Applied along with some other hacking to reduce the costs of the
lower-level functions that this example shows to be inefficient.
They'd still be slow in large queries, whether CE applies or not.
BIG difference. The case that caused swapping and took almost
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
Applied along with some other hacking to reduce the costs of the
lower-level functions that this example shows to be inefficient.
They'd still be slow in large queries, whether CE applies or not.
BIG difference. The
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
Applied along with some other hacking to reduce the costs of the
lower-level functions that this example shows to be inefficient.
They'd still be slow in large queries, whether CE applies or not.
BIG difference. The
Magnus Hagander wrote:
Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
No, it's definitly the right primitive. But we're creating it with a max
count of 1.
That's definitely wrong. There are at least three reasons for a PG
process's semaphore to be signaled
Well, I'm thinking in define (maybe via SQL) a set of servers as a
cluster and make the fragmentation rules based on select clauses,
storing this configuration in a specific catalog in global schema.
For example: when a record is inserted in a server which not store
this fragment (no rule
On Sat, 2007-04-21 at 02:38 -0400, Tom Lane wrote:
Maybe so, but you're going to be writing quite a lot of duplicative
code, because the existing routines you might have been thinking of
using (lsyscache.c etc) don't behave that way.
Right, I'm envisioning doing a conditional LockAcquire and
On Sat, 2007-04-21 at 17:56 -0400, Neil Conway wrote:
Right, I'm envisioning doing a conditional LockAcquire and then
heap_open() / heap_getnext() by hand. That will be relatively slow, but
code that emits a deadlock error message is almost by definition not
performance critical.
... although
Hello,
I translated some things and I corrected many others in the
translation of pgadmin3 for Portuguese of Brazil. It incorrectly had
much translated thing, and much thing with translation of one another
one. It would like to know you as I can disponibilizar this my small
contribution.
--
Nabucodonosor Coutinho wrote:
I translated some things and I corrected many others in the
translation of pgadmin3 for Portuguese of Brazil. It incorrectly had
much translated thing, and much thing with translation of one another
one. It would like to know you as I can disponibilizar this my
Dave Page [EMAIL PROTECTED] writes:
I've been seeing this failure intermittently on Narwhal HEAD, and once
on 8.1. Other branches have been OK, as have other animals running on
the same physical box. Narwhal-HEAD is run more often than any other
builds however.
Anyone have any idea what
ops, error when typing the name of the list. excuses
2007/4/21, Euler Taveira de Oliveira [EMAIL PROTECTED]:
Nabucodonosor Coutinho wrote:
I translated some things and I corrected many others in the
translation of pgadmin3 for Portuguese of Brazil. It incorrectly had
much translated thing,
I wrote:
I'm still feeling a bit annoyed with the behavior of the stats machinery
(pgstat_initstats and related macros).
... That means more UDP traffic and more work for
the stats collector. gprof won't show the resulting overhead since
it doesn't know anything about kernel-level overhead
21 matches
Mail list logo
