On Fri, Dec 23, 2005 at 11:19:01PM -0500, Rod Taylor wrote:
In many cases you could use temporary tables, but sometimes you might want
multiple processes or multiple transactions to be able to see the data.
Could always implement GLOBAL TEMP tables that have the ability to use
these kinds
I've gotten interested again in the issue of row comparisons, eg
(a, b, c) = (1, 2, 3)
We've discussed this before, the most comprehensive thread being
http://archives.postgresql.org/pgsql-performance/2004-07/msg00188.php
but nothing's gotten done. Unless someone's already working on
I have found long standing bug with with certain Asian multibyte
charsets handling(original report was made by Mr. Ishida).
Some text operations on certain Asian charsets such as EUCj-JP code
set 3 (JIS X 0212) make wrong results. As far as I know, these
include:
- strpos
- regular expression
On Fri, Dec 23, 2005 at 03:18:21PM -0500, Tom Lane wrote:
I've gotten interested again in the issue of row comparisons, eg
(a, b, c) = (1, 2, 3)
We've discussed this before, the most comprehensive thread being
http://archives.postgresql.org/pgsql-performance/2004-07/msg00188.php
but
Now, since COLLATE support is still in progress, I'm not sure how much
any of this helps you. I'm up to modifying the scankeys but it's hard
when you jave to keep rgrepping the tree to work out what is called
from where...
src/tools/make_ctags is your friend...
Chris
The TODO list has an item add missing date selectivity, which is a
hang-over from 1999 or before.
Is this still an issue? Can somebody describe exactly what it is?
I can't find the exact discussion of what the problem was/is, so its
better to ask directly...
Best Regards, Simon Riggs
On Sat, Dec 24, 2005 at 06:05:58PM +0800, Christopher Kings-Lynne wrote:
Now, since COLLATE support is still in progress, I'm not sure how much
any of this helps you. I'm up to modifying the scankeys but it's hard
when you jave to keep rgrepping the tree to work out what is called
from
Am Samstag, 24. Dezember 2005 11:46 schrieb Martijn van Oosterhout:
That just shows you where a symbol is defined, not where it's called
from.
I've never used ctags, but etags certainly do what you ask for.
---(end of broadcast)---
TIP 3: Have
On Sat, Dec 24, 2005 at 12:25:41PM +0100, Peter Eisentraut wrote:
Am Samstag, 24. Dezember 2005 11:46 schrieb Martijn van Oosterhout:
That just shows you where a symbol is defined, not where it's called
from.
I've never used ctags, but etags certainly do what you ask for.
Really? I've
On Fri, 2005-12-23 at 22:41 -0500, Greg Stark wrote:
Tom Lane [EMAIL PROTECTED] writes:
Qingqing Zhou [EMAIL PROTECTED] writes:
I revised the idea with MINIMAL XLOG (instead of WITHOUT XLOG) like the
below. I think in this way, we can always gaurantee its correctness and
can always
Martijn van Oosterhout kleptog@svana.org writes:
One thing my COLLATE patch does is distinguish between collations and
operator classes. So the reverse operator class issue disappears
because it's just a collation and doesn't need a operator class
(although it won't break anything, see below).
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Now, since COLLATE support is still in progress, I'm not sure how much
any of this helps you. I'm up to modifying the scankeys but it's hard
when you jave to keep rgrepping the tree to work out what is called
from where...
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Can someone explain to me how:
(a, b) (1, 2)
is different to
a 1 and b 2
Right at the moment our code interprets it that way, but this behavior
is wrong per spec. It should be an ordered column-by-column comparison,
so that the equivalent
Martijn van Oosterhout kleptog@svana.org writes:
CREATE GLOBAL TEMP TABLE blah INHERITS myhugetable;
I don't think you can have your temp table inherit from a real table. That
would make your real table have temp table semantics. Ie, records in it will
spontaneously disappear on reboot.
But
Greg Stark [EMAIL PROTECTED] writes:
Martijn van Oosterhout kleptog@svana.org writes:
CREATE GLOBAL TEMP TABLE blah INHERITS myhugetable;
I don't think you can have your temp table inherit from a real table.
Bear in mind also that this notion of a GLOBAL TEMP table has less than
nothing to do
[moving to -hackers]
Peter Eisentraut wrote:
Am Samstag, 24. Dezember 2005 00:20 schrieb Andrew Dunstan:
The rationale is one connection per apache thread (which on Windows
defaults to 400). If people think this is too many I could live with
winding it back a bit - the defaults number of
Andrew Dunstan [EMAIL PROTECTED] writes:
Maybe we need to split this into two pieces, given Tom's legitimate
concern about semaphore use. How about we increase the allowed range for
shared_buffers and max_fsm_pages, as proposed in my patch, and leave the
max_connections issue on the table?
Tom Lane wrote:
BTW, I fat-fingered the calculations I was doing last night --- the
actual shmem consumption in CVS tip seems to be more like 17K per
max_connection increment, assuming max_locks_per_connection = 64.
ITYM max_locks_per_transaction (which as the docs say is confusingly
Robert Treat wrote:
Maybe we should write something in to check if apache is installed if we're so
concerned about that usage...
Er, yeah, I'll get right on that. (Don't hold your breath.)
I already know that I set the connection limits
lower on most of the installations I do (given
Hello,
Just a small thank you to all the developers of PostgreSQL for making
2005 another incredible year for Command Prompt, Inc.
Command Prompt hopes to continue increasing it's community contributions
next year.
Merry Christmas everyone!
Sincerely,
Joshua D. Drake
President
Command
On Thu, 22 Dec 2005 10:40:24 -0500, Tom Lane [EMAIL PROTECTED]
wrote:
If you move items
from one page to the other in the opposite direction from the way the
scan is going, then it will miss those items.
AFAIU the (PG implementaion of the) LY method is designed to make
scans immune against
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
We already do something similar for page deletions. Empty pages are not
deleted right away, but they are marked with BTP_DEAD, and then deleted
on a subsequent vacuum. Or something like that, I don't remember the
exact details.
[moved to -hackers]
Petr Jelinek said:
Andrew Dunstan wrote:
Just because we can run with very little memory doesn't mean we have to.
What is the point of having lots of memory if you don't use it? We are
talking defaults here. initdb will still scale down on
resource-starved machines.
Martijn van Oosterhout wrote:
src/tools/make_ctags is your friend...
That just shows you where a symbol is defined, not where it's called
from. When you change the parameters of a function, you need to make
sure you found all the places that used it...
IOW, it's good for going down the
Manfred Koizar [EMAIL PROTECTED] writes:
BTW, if after having locked both pages we find that we have
super-exclusive locks, i.e. nobody else has pins on these pages, we
can reorganize much more agressively.
No, we cannot. I'm getting tired of explaining this.
regards,
Kevin Brown [EMAIL PROTECTED] writes:
Well, REINDEX is apparently a very expensive operation right now. But
how expensive would it be to go through the entire index and perform
the index page merge operation being discussed here, and nothing else?
If it's fast enough, might it be worthwhile
To the PostgreSQL Community:
All of us at EnterpriseDB want to thank the community for
creating an amazing base upon which to build our new company. Its been a
busy year for us, going from zero to 70 people, raising venture capital, and
working hard to promote both PostgreSQL itself and
27 matches
Mail list logo
