Simon Riggs wrote:
...knock-on...
tackle
Been watching the Rugby World Cup? :)
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes
Simon Riggs wrote:
I'm a bit surprised the TODO didn't mention the MERGE statement, which
is the SQL:2003 syntax for specifying this as an atomic statement.
http://archives.postgresql.org/pgsql-hackers/2004-05/thrd5.php#00497
There is a thread there entitled Adding MERGE to the TODO list
Tom Lane wrote:
Bricklen Anderson [EMAIL PROTECTED] writes:
http://archives.postgresql.org/pgsql-hackers/2004-05/thrd5.php#00497
There is a thread there entitled Adding MERGE to the TODO list
The more interesting discussion is the one that got it taken off TODO again,
from Nov 2005. Try
Tom Lane wrote:
And if so, would you mind stopping your mail system from regurgitating
copies of pghackers traffic? It's especially bad that you're sending
the stuff with a fraudulent envelope From, ie, one not pointing back
at yourself.
That would be me. I've notified one of our admins
J. Andrew Rogers wrote:
snip
A graphical installer for Unix is fine, but please, do not make it
anything like Oracle's graphical installer. Oracle's graphical install
process gives command line installs a good name for ease of use.
J. Andrew Rogers
I heartily second that!
Michael Fuhr wrote:
Rollback Mountain
A raw, powerful story of two young transactions, one serializable
and the other read-committed, who meet in the summer of 2005 updating
tables in the harsh, high-volume environment of a contemporary
online trading system and form an unorthodox yet
Qingqing Zhou wrote:
I am not sure if this idea was mentioned before.
The basic prefix btree idea is quite straightforward, i.e., try to
compress the key items within a data page by sharing the common prefix.
Thus the fanout of the page is increased and the benefits is obvious
Paolo Magnoli wrote:
Hi, I seem to recall that in Oracle you load into specific partitions
without specifically naming them in insert statements (in other words you
insert into table, the engine redirects data to the corrisponding
partition),
This is correct
--
Jonah H. Harris wrote:
Hey everyone,
I'm sure this has been thought of but was wondering whether anyone had
discussed the allowance of run-time block size specifications at the
tablespace level? I know that a change such as this would substantially
impact buffer operations, transactions,
