-Original Message-
From: Hannu Krosing [mailto:[EMAIL PROTECTED]
Sent: Monday, June 11, 2007 10:43 PM
To: Larry McGhaw
Cc: Tom Lane; Alvaro Herrera; Dann Corbit; Gregory Stark; Martijn van
Oosterhout; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Selecting a constant question
-Original Message-
From: Cui Shijun [mailto:[EMAIL PROTECTED]
Sent: Friday, June 08, 2007 11:11 PM
To: Dann Corbit
Cc: Jim C. Nasby; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Issues with factorial operator
Hi,
2007/6/9, Dann Corbit [EMAIL PROTECTED]:
It makes sense
-Original Message-
[snip]
Hum... I think there is a little improvement: when n is too large,(say
n10, 000) we can use Stirling's formula to get the estimated value of
n!:-)
Or (rather) the log base 10 of Stirling's formula. The n! estimator
will overflow for sure, unless we take
We have (among other things) and ODBC/OLEDB/JDBC/.NET driver for
PostgreSQL and we want to optimize fast mode insert/select behavior.
When we try to do a binary mode copy from standard input, we get an
error message that we can't do it.
How can we programmatically insert data using COPY
It makes sense with factorial function to do an error check on the
domain. Calculate beforehand, and figure out what the largest sensible
domain value is.
For instance, in Maple, I get this:
y:=92838278!;
Error, object too large
The error message returns instantly.
For reasonably large
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Joshua D. Drake
Sent: Friday, June 08, 2007 10:49 PM
To: Alvaro Herrera
Cc: Matthew T. O'Connor; Jim C. Nasby; Michael Paesold; Tom Lane; Andrew
Hammond; Peter Eisentraut;
Clients using pqlib can get some boost by increasing tcp/ip window size.
It might be good to make it a settable parameter.
Anyway, maybe something like this:
/* --
* connectNoDelay -
* Sets the TCP_NODELAY socket option.
* Returns 1 if successful, 0 if not.
* --
*/
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Thursday, May 10, 2007 11:53 AM
To: Neil Conway
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Planning large IN lists
Neil Conway [EMAIL PROTECTED] writes:
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Alvaro Herrera
Sent: Friday, April 13, 2007 4:24 PM
To: Tom Lane
Cc: [EMAIL PROTECTED]; PostgreSQL Performance; Steve
Subject: Re: [HACKERS] choose_bitmap_and again (was Re: [PERFORM]
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-general-
[EMAIL PROTECTED] On Behalf Of Thomas Kellerer
Sent: Friday, October 13, 2006 2:11 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] more anti-postgresql FUD
[EMAIL PROTECTED] wrote on 11.10.2006 16:54:
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Greg Stark
Sent: Tuesday, August 01, 2006 4:42 PM
To: Hannu Krosing
Cc: Andrew Dunstan; Gregory Stark; Tom Lane; Alvaro Herrera; Jim C. Nasby;
Luke Lonergan; [EMAIL PROTECTED]; Bruce
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Luke Lonergan
Sent: Friday, July 28, 2006 12:18 PM
To: Jim C. Nasby; Jie Zhang
Cc: Tom Lane; Mark Kirkwood; Josh Berkus; Gavin Sherry; pgsql-
[EMAIL PROTECTED]
Subject: Re: [HACKERS]
I sent him a copy
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jonah H. Harris
Sent: Thursday, March 16, 2006
11:43 AM
To: Tom Lane
Cc: pgsql-hackers@postgresql.org;
Jerry Sievers
Subject: Re: [HACKERS] qsort, once
again
On 3/16/06, Tom Lane [EMAIL
. Small number of distinct values
Then it will cause problems in real-life use.
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 16, 2006 12:09 PM
To: Dann Corbit
Cc: Jonah H. Harris; pgsql-hackers@postgresql.org; Jerry Sievers
Subject: Re: [HACKERS
[snip]
So at least on randomized data, the swap_cnt thing is a serious loser.
Need to run some tests on special-case inputs though. Anyone have a
test suite they like?
regards, tom lane
Here is a distribution maker that will create some torture tests for
sorting
Actually, if you compile with CREATE_DISTRIBS defined, it does define a
main() function and create sample distributions.
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Dann Corbit
Sent: Thursday, March 16, 2006 1:28 PM
To: Tom Lane
-Original Message-
From: Dann Corbit
Sent: Thursday, March 16, 2006 1:31 PM
To: Dann Corbit; Tom Lane; Jonah H. Harris
Cc: pgsql-hackers@postgresql.org; Jerry Sievers
Subject: RE: [HACKERS] qsort, once again
Actually, if you compile with CREATE_DISTRIBS defined, it does define
a
main() function
So my feeling is we should just remove the swap_cnt code and return to
the original BM algorithm. Being much faster than expected for
presorted input doesn't justify being far slower than expected for
other inputs, IMHO. In the context of Postgres I doubt that perfectly
sorted input shows
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Dann Corbit
Sent: Thursday, March 16, 2006 4:42 PM
To: Tom Lane
Cc: Jonah H. Harris; pgsql-hackers@postgresql.org; Jerry Sievers
Subject: Re: [HACKERS] qsort, once again
So my
Well, my point was that it is a snap to implement and test.
It will be better, worse, or the same.
I agree that Bentley is a bloody genius.
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 16, 2006 9:27 PM
To: Dann Corbit
Cc: Jonah H. Harris; pgsql
-Original Message-
From: Stephen Frost [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 09, 2006 3:49 PM
To: Tom Lane
Cc: Luke Lonergan; Jim C. Nasby; Greg Stark; Dann Corbit; Simon Riggs;
pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Merge algorithms for large numbers of tapes
I do not clearly understand the sorting code in PostgreSQL. If I did
have a good grasp of it, I would take a go at improving it.
Here are some suggestions of things that I know work really, really
well:
#1. Two pass merge (none of that silly poly-tape merge goo)
#2. Load ONLY the keys that
-Original Message-
From: Luke Lonergan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 1:52 PM
To: Dann Corbit; Tom Lane; Jim C. Nasby
Cc: Simon Riggs; pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] Merge algorithms for large numbers of tapes
Dann,
On 3/8/06 12
There are some articles here that are worth reading if you want to sort
fast:
http://research.microsoft.com/barc/SortBenchmark/
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Dann Corbit
Sent: Wednesday, March 08, 2006 1:59 PM
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 3:17 PM
To: Dann Corbit
Cc: Jim C. Nasby; Luke Lonergan; Simon Riggs;
pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Merge algorithms for large numbers of tapes
Dann Corbit [EMAIL
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 3:56 PM
To: Luke Lonergan
Cc: Dann Corbit; Tom Lane; Jim C. Nasby; Simon Riggs; pgsql-
[EMAIL PROTECTED]
Subject: Re: [HACKERS] Merge algorithms for large numbers of tapes
Luke
-Original Message-
From: Jim C. Nasby [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 5:44 PM
To: Dann Corbit
Cc: Tom Lane; Luke Lonergan; Simon Riggs; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Merge algorithms for large numbers of tapes
On Wed, Mar 08, 2006
Use a priority queue for the sorted sub-lists.
When the key-object extracted from the head of the smallest queue exceeds the key-object
from the head of the second queue, adjust the priority of the smallest queue
within the list of queues.
It uses a total of 2 read/write passes
over the
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Markus Schaber
Sent: Thursday, February 16, 2006 5:45 AM
To: pgsql-performance@postgresql.org; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] qsort again (was Re: [PERFORM] Strange
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Wednesday, February 15, 2006 5:22 PM
To: Ron
Cc: pgsql-performance@postgresql.org; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] qsort again (was Re: [PERFORM]
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Josh Berkus
Sent: Thursday, January 19, 2006 10:09 AM
To: Martijn van Oosterhout
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Surrogate keys (Was: enums)
Martjin,
In
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Josh Berkus
Sent: Wednesday, January 18, 2006 3:59 PM
To: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Surrogate keys (Was: enums)
Martjin,
Interesting. However, in my
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Dann Corbit
Sent: Wednesday, January 18, 2006 4:04 PM
To: josh@agliodbs.com; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Surrogate keys (Was: enums)
-Original Message
Maybe it goes better into Advocacy or something, but I have found a quote by
database big-wigs that I strongly disagree with:
From:
http://www.db.ucsd.edu/cse132B/Thirdmanifesto.pdf
We have this.
PROPOSITION 1.4: Unique Identifiers (UIDs) for records should be assigned by
the DBMS only if a
-Original Message-
From: Michael Glaesemann [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 18, 2006 5:48 PM
To: Dann Corbit
Cc: Leandro Guimarães Faria Corcete Dutra; Jim C. Nasby; pgsql-
[EMAIL PROTECTED]
Subject: Re: [HACKERS] Surrogate keys (Was: enums)
On Jan 19, 2006
: Tom Lane; Dann Corbit; Qingqing Zhou; Bruce Momjian; Luke
Lonergan;
Neil Conway; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Re: Which qsort is used
On Thu, 22 Dec 2005 08:01:00 +0100, Martijn van Oosterhout
kleptog@svana.org wrote:
But where are you including the cost to check how
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 15, 2005 6:24 PM
To: Dann Corbit
Cc: Qingqing Zhou; Greg Stark; Jim C. Nasby; Luke Lonergan; Neil
Conway;
Bruce Momjian; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Which qsort is used
is used
On Fri, 16 Dec 2005, Bruce Momjian wrote:
At this point, I think we have done enough testing on enough
platforms
to just use port/qsort on all platforms in 8.2. It seems whenever
someone tries to improve the BSD qsort, they make it worse.
Not necessariliy true. Dann Corbit
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Friday, December 16, 2005 9:03 PM
To: Dann Corbit
Cc: Qingqing Zhou; Bruce Momjian; Luke Lonergan; Neil Conway; pgsql-
[EMAIL PROTECTED]
Subject: Re: [HACKERS] Re: Which qsort is used
Dann Corbit [EMAIL PROTECTED
-Original Message-
From: Qingqing Zhou [mailto:[EMAIL PROTECTED]
Sent: Friday, December 16, 2005 10:13 PM
To: Dann Corbit
Cc: Tom Lane; Bruce Momjian; Luke Lonergan; Neil Conway; pgsql-
[EMAIL PROTECTED]
Subject: RE: [HACKERS] Re: Which qsort is used
On Sat, 17 Dec 2005, Dann
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Friday, December 16, 2005 10:41 PM
To: Dann Corbit
Cc: Qingqing Zhou; Bruce Momjian; Luke Lonergan; Neil Conway; pgsql-
[EMAIL PROTECTED]
Subject: Re: [HACKERS] Re: Which qsort is used
Dann Corbit [EMAIL PROTECTED
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Qingqing Zhou
Sent: Thursday, December 15, 2005 3:16 PM
To: Greg Stark
Cc: Jim C. Nasby; Luke Lonergan; Tom Lane; Neil Conway; Bruce Momjian;
pgsql-hackers@postgresql.org
Subject: Re:
Here is a sort template (that can very easily be turned into a C
routine).
It is an introspective sort. Bentley McIlroy proved that every qsort
routine will degrade into quadratic behavior with a worst-case input.
This function detects quadratic behavior and switches to qsort when
needed.
Use
Strike switches to qsort insert switches to heapsort
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Dann Corbit
Sent: Tuesday, December 13, 2005 10:40 AM
To: Qingqing Zhou; Luke Lonergan
Cc: Tom Lane; Neil Conway; Bruce Momjian
The test is O(n)
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 13, 2005 10:51 AM
To: Dann Corbit
Cc: Qingqing Zhou; Luke Lonergan; Neil Conway; Bruce Momjian; pgsql-
[EMAIL PROTECTED]
Subject: Re: [HACKERS] Which qsort is used
Dann Corbit
quadratic
(without a test). Of course, introspective sort does not suffer from
this defect, even with the test removed.
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Dann Corbit
Sent: Tuesday, December 13, 2005 11:53 AM
To: Tom Lane
Cc
I will send you an ANSI C version.
-Original Message-
From: Qingqing Zhou [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 13, 2005 1:08 PM
To: Dann Corbit
Cc: Tom Lane; Luke Lonergan; Neil Conway; Bruce Momjian; pgsql-
[EMAIL PROTECTED]
Subject: RE: [HACKERS] Which qsort is used
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 13, 2005 7:38 PM
To: Dann Corbit
Cc: Qingqing Zhou; Luke Lonergan; Neil Conway; Bruce Momjian; pgsql-
[EMAIL PROTECTED]
Subject: Re: [HACKERS] Which qsort is used
Dann Corbit [EMAIL PROTECTED
A general purpose log miner is also useful
in many other areas besides replication.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jonah H. Harris
Sent: Thursday, December 08, 2005
11:32 AM
To: Jim C. Nasby
Cc: Darcy Buskermolen;
pgsql-hackers@postgresql.org;
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Thursday, November 17, 2005 4:17 PM
To: Simon Riggs
Cc: Kevin Grittner; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Improving count(*)
Simon Riggs [EMAIL
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Simon Riggs
Sent: Wednesday, November 16, 2005 10:35 AM
To: Martijn van Oosterhout
Cc: Bruce Momjian; Rick Gigger; Tom Lane; Christopher Kings-Lynne; Jim
C.
Nasby; josh@agliodbs.com;
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Magnus Hagander
Sent: Friday, November 04, 2005 10:31 AM
To: Tom Lane; Merlin Moncure
Cc: pgsql-hackers@postgresql.org; pgsql-performance@postgresql.org
Subject: Re: [HACKERS] [PERFORM]
Document the collating sequences used for the character types.
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: Monday, October 24, 2005 11:01 AM
To: Tom Lane
Cc: Dann Corbit; [EMAIL PROTECTED];
[EMAIL PROTECTED];
pgsql-hackers@postgresql.org
Subject: Re
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: Monday, October 24, 2005 5:57 PM
To: Dann Corbit
Cc: Tom Lane; [EMAIL PROTECTED]; [EMAIL PROTECTED];
pgsql-hackers@postgresql.org
Subject: Re: [GENERAL] [HACKERS] 'a' == 'a '
Dann Corbit wrote:
Document
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Greg Stark
Sent: Wednesday, October 19, 2005 11:17 PM
To: Tom Lane
Cc: Chris Travers; josh@agliodbs.com; pgsql-hackers@postgresql.org;
Dann
Corbit; Stephan Szabo; Terry Fielder; Tino
-Original Message-
From: Chris Travers [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 20, 2005 11:53 AM
To: Dann Corbit
Cc: Greg Stark; Tom Lane; Chris Travers; josh@agliodbs.com; pgsql-
[EMAIL PROTECTED]; Stephan Szabo; Terry Fielder; Tino Wildenhain;
Marc G. Fournier; [EMAIL
, 2005 12:53 PM
To: Dann Corbit
Cc: pgsql-hackers@postgresql.org; pgsql-general General
Subject: Re: [GENERAL] [HACKERS] 'a' == 'a '
[Removed all the non-list addresses]
Dann Corbit wrote:
Let me make something clear:
When we are talking about padding here it is only in the context
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, October 20, 2005 2:12 PM
To: Tom Lane
Cc: Chris Travers; Dann Corbit; Greg Stark; josh@agliodbs.com; pgsql-
[EMAIL PROTECTED]; pgsql-hackers@postgresql.org; Marc G.
Fournier;
Stephan Szabo; Terry
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 20, 2005 2:54 PM
To: Dann Corbit
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; pgsql-
[EMAIL PROTECTED]
Subject: Re: [GENERAL] [HACKERS] 'a' == 'a '
Dann Corbit [EMAIL PROTECTED] writes:
I guess
a space. Is that the case for PostgreSQL? Even
if it is, is seems truly bizarre that the NO PAD attribute would be
applied to string constants.
-Original Message-
From: Marc G. Fournier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 19, 2005 12:53 PM
To: Dann Corbit
Cc: Stephan Szabo
of it.
-Original Message-
From: Tino Wildenhain [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 19, 2005 1:05 PM
To: Marc G. Fournier
Cc: Dann Corbit; [EMAIL PROTECTED]; pgsql-
[EMAIL PROTECTED]; pgsql-general@postgresql.org
Subject: Re: 'a' == 'a ' (Was: RE: [pgsql-advocacy] [GENERAL
-Original Message-
From: Terry Fielder [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 19, 2005 2:05 PM
To: Dann Corbit
Cc: Tino Wildenhain; Marc G. Fournier; [EMAIL PROTECTED];
pgsql-hackers@postgresql.org; pgsql-general@postgresql.org
Subject: Re: 'a' == 'a ' (Was: RE: [pgsql
-Original Message-
From: Stephan Szabo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 19, 2005 2:34 PM
To: Dann Corbit
Cc: Terry Fielder; Tino Wildenhain; Marc G. Fournier;
[EMAIL PROTECTED]; pgsql-hackers@postgresql.org; pgsql-
[EMAIL PROTECTED]
Subject: Re: [HACKERS
-Original Message-
From: Martijn van Oosterhout [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 19, 2005 2:46 PM
To: Dann Corbit
Cc: Terry Fielder; Tino Wildenhain; Marc G. Fournier;
[EMAIL PROTECTED]; pgsql-hackers@postgresql.org; pgsql-
[EMAIL PROTECTED]
Subject: Re
a
blockhead like me can comprehend it easily.
-Original Message-
From: Josh Berkus [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 19, 2005 5:06 PM
To: pgsql-hackers@postgresql.org
Cc: Dann Corbit; Stephan Szabo; Terry Fielder; Tino Wildenhain; Marc G.
Fournier; [EMAIL PROTECTED]; pgsql
As an aside, here is a package that has recently been BSD re-licensed:
http://sourceforge.net/projects/libltx/
It is a lightweight memory transaction package. It comes with a paper
entitled Cache Sensitive Software Transactional Memory by Robert
Ennals.
In the paper, Robert Ennals suggests
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Lane Van Ingen
Sent: Monday, October 10, 2005 12:41 PM
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] Need A Suggestion
I am working on the development of a military application
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Friday, September 30, 2005 11:02 PM
To: Jeffrey W. Baker
Cc: Luke Lonergan; Josh Berkus; Ron Peacetree; pgsql-
[EMAIL PROTECTED]; pgsql-performance@postgresql.org
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of PFC
Sent: Thursday, September 29, 2005 9:10 AM
To: [EMAIL PROTECTED]
Cc: Pg Hackers; pgsql-performance@postgresql.org
Subject: Re: [HACKERS] [PERFORM] A Better External Sort?
I see the following routines that seem to be related to sorting.
If I were to examine these routines to consider ways to improve it, what
routines should I key in on? I am guessing that tuplesort.c is the hub
of activity for database sorting.
Directory of
by Dann Corbit and Pete Filandr.
** ([EMAIL PROTECTED] and [EMAIL PROTECTED])
** Use it however you like.
*/
//
// The insertion sort template is used for small partitions.
//
template class e_type
void insertion_sort(e_type * array, size_t nmemb)
{
e_type temp,
*last
Judy definitely rates a WOW!!
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Gregory Maxwell
Sent: Friday, September 30, 2005 7:07 PM
To: Ron Peacetree
Cc: Jeffrey W. Baker; pgsql-hackers@postgresql.org; pgsql-
[EMAIL PROTECTED]
If I were to be nosy and poke around in this, what patches of code would
I be interested in?
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Josh Berkus
Sent: Thursday, September 29, 2005 11:28 AM
To: pgsql-hackers@postgresql.org
Cc:
-Original Message-
From: Ron Peacetree [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 24, 2005 3:31 AM
To: Dann Corbit; pgsql-hackers@postgresql.org; pgsql-
[EMAIL PROTECTED]
Subject: RE: [HACKERS] [PERFORM] Releasing memory during External
sorting?
From: Dann Corbit [EMAIL
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Ron Peacetree
Sent: Monday, September 26, 2005 10:47 AM
To: pgsql-hackers@postgresql.org; pgsql-performance@postgresql.org
Subject: [HACKERS] [PERFORM] A Better External Sort?
From:
Generally, when you read from a set of
subfiles, the OS will cache the reads to some degree, so the disk-seek jitter
is not always that bad. On a highly fragmented disk drive, you might also jump
all over the place reading serially from a single subfile. Of course,
every situation is
For the subfiles, load the top element of each subfile into a priority
queue. Extract the min element and write it to disk. If the next value
is the same, then the queue does not need to be adjusted. If the next
value in the subfile changes, then adjust it.
Then, when the lowest element in the
PROTECTED] On Behalf Of Dann Corbit
Sent: Friday, September 23, 2005 2:21 PM
To: Ron Peacetree; Mark Lewis; Tom Lane; pgsql-hackers@postgresql.org;
pgsql-performance@postgresql.org
Subject: Re: [HACKERS] [PERFORM] Releasing memory during External
sorting?
For the subfiles, load the top element
To find out about boolean logic, take a look here:
http://www.laynetworks.com/Boolean%20Algebra.htm
Where I work, we took the SIS toolkit from Berkeley and did a
simplification of the where clause as if it was a Boolean integrated
circuit. Of course, you may get answers that you do not expect if
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Tino Wildenhain
Sent: Monday, September 12, 2005 3:04 AM
To: [EMAIL PROTECTED]
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Materialized Views in PostgreSQL
Jean-Michel
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Josh Berkus
Sent: Tuesday, September 06, 2005 6:40 PM
To: [EMAIL PROTECTED]
Cc: Bob Ippolito; [EMAIL PROTECTED];
pgsql-hackers@postgresql.org;
nathan wagner
Subject: Re: [HACKERS] uuid
centuries that are divisible by 4000 thus giving an accuracy
of about one day in 20,000 years
I think either approach would be fine as long as it is documented
exactly that the calculation does.
-Original Message-
From: Dann Corbit
Sent: Friday, July 22, 2005 12:24 PM
To: 'Bruce Momjian
-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: Friday, July 22, 2005 12:03 PM
To: Bruno Wolff III
Cc: Dann Corbit; Greg Stark; Tino Wildenhain; Tom Lane; PostgreSQL-
development; Marc G. Fournier
Subject: Re: [HACKERS] Imprecision of DAYS_PER_MONTH
Bruno Wolff III wrote:
On Thu
In round figures:
Since there are 365.2422 days per tropical year, there are 31556926
seconds per year (give or take leap seconds).
Ref:
http://www.grc.nasa.gov/WWW/K-12/Numbers/Math/Mathematical_Thinking/cale
ndar_calculations.htm
So 31557600 seems to be off by quite a bit.
-Original
I probably shouldn't jump in, because I do not know the nature of the
usage of the CRC values.
But if the birthday paradox can come into play, with a 32 bit CRC, you
will get one false mismatch every 78,643 items or so.
http://mathworld.wolfram.com/BirthdayProblem.html
Probably you already knew
.
-Original Message-
From: Rada Chirkova [mailto:[EMAIL PROTECTED]
Sent: Friday, May 13, 2005 2:55 PM
To: Rada Chirkova
Cc: Dann Corbit
Subject: Re: Do you have any objections on contributing your
improvements
of the PostgreSQL core back into the product?
Dear Dann Corbit, could you tell me
to know if the PG group would want this work to be done.
I am sure that she expects code reviews and beta tests and all the other
standard fare.
-Original Message-
From: Josh Berkus [mailto:[EMAIL PROTECTED]
Sent: Friday, May 13, 2005 4:03 PM
To: Dann Corbit
Cc: pgsql-hackers
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, May 09, 2005 5:36 PM
To: Dann Corbit
Subject: RE: Priority Mechanisms for OLTP and Transactional Web
Applications
So how should we move forward on this? Do you have an application in
mind
Suggestion:
Use INFORMATION_SCHEMA for everything that INFORMATION_SCHEMA covers.
That way, there will not be needless duplications.
Create new tables with foreign keys to the INFORMATION_SCHEMA for
everything else.
Alternative suggestion:
Create any sort of magic, pg-specific schema you want,
If the idea originates in PostgreSQL, then nobody else can patent it,
because there will be pre-existing art (the PostgreSQL engine) that
already demonstrated the idea. A patent must have a novel idea in it.
I do not think a good thing can come from creation of software patents.
Here is a link
benefit PostgreSQL in interesting ways.
-Original Message-
From: Rada Chirkova [mailto:[EMAIL PROTECTED]
Sent: Friday, May 06, 2005 7:53 AM
To: Dann Corbit; rada Chirkova
Subject: Re: Do you have any objections on contributing your
improvements
of the PostgreSQL core back
Why not tack on the missing functionality to the INFORMATION_SCHEMA views?
A couple of new tables and foreign keys should do it, n'est ce pas?
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Josh Berkus
Sent: Wednesday, May 04, 2005
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Josh Berkus
Sent: Thursday, May 05, 2005 10:49 AM
To: Andreas Pflug
Cc: PostgreSQL-development
Subject: Re: [HACKERS] Views, views, views! (long)
Andreas,
There are only two
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Andrew - Supernews
Sent: Thursday, May 05, 2005 4:55 PM
To: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Views, views, views! (long)
On 2005-05-05, Josh Berkus
INFORMATION_SCHEMA is what should be exposed to the end-users of
PostgreSQL.
Pg_schema (for lack of a better name for internal metadata) can be
useful as well for all sorts of special purposes. Probably,
INFORMATION_SCHEMA (as designed by the SQL Standards committee) does not
need to worry about
-Original Message-
From: Josh Berkus [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 05, 2005 5:35 PM
To: Dann Corbit
Cc: elein; PostgreSQL-development; Peter Eisentraut
Subject: Re: [HACKERS] Views, views, views! (long)
Dann,
1. There is not a whole lot of stuff that cannot
PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 04, 2005 11:40 AM
To: Dann Corbit
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Priority Mechanisms for OLTP and Transactional Web
Applications
In our experimentation, we simply used a user
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 04, 2005 12:44 PM
To: Dann Corbit
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: Priority Mechanisms for OLTP and Transactional Web
Applications
Dear
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 04, 2005 12:44 PM
To: Dann Corbit
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: Priority Mechanisms for OLTP and Transactional Web
Applications
As someone who has made a few minor contributions and plenty of
suggestions, but who is not on the core team, I would like to offer my
observations.
Every suggestion I have ever made that had any merit at all has
eventually worked its way into PostgreSQL (most -- perhaps all -- were
already under
101 - 200 of 433 matches
Mail list logo
