Magnus Hagander <[EMAIL PROTECTED]> writes:
> On Fri, 2007-11-09 at 02:26 -0500, Tom Lane wrote:
>> Plan B would be to take out contracts on all the banana-republic
>> politicians who think that changing DST laws with a month's notice
>> is a pleasant pastime. I fear we lack the resources for that
On Nov 9, 2007 3:08 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> This rule works for all the locales I have installed ... but I don't
> have any Far Eastern locales installed. Also, my test cases are only
> covering ASCII characters, and I believe many locales have some non-ASCII
> letters that sort
On Thu, 2007-11-08 at 23:04 +, Gregory Stark wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
>
> > The pages might well be in cache, so the file location might well be
> > irrelevant from an I/O perspective. Maybe. The nth page solution allows
> > the FSM block to be easily located without
On Fri, 2007-11-09 at 02:26 -0500, Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> > On Thu, Nov 08, 2007 at 05:46:08PM -0800, Trevor Talbot wrote:
> >> I've been wondering lately why it isn't just stored in the database
> >> somewhere.
>
> > That's a different question. One reas
Magnus Hagander <[EMAIL PROTECTED]> writes:
> On Thu, Nov 08, 2007 at 05:46:08PM -0800, Trevor Talbot wrote:
>> I've been wondering lately why it isn't just stored in the database
>> somewhere.
> That's a different question. One reason is that we wanted files compatible
> with the stuff that was
On Thu, Nov 08, 2007 at 05:46:08PM -0800, Trevor Talbot wrote:
> On 11/8/07, Magnus Hagander <[EMAIL PROTECTED]> wrote:
>
> > Andrew Dunstan wrote:
> > > Tom Lane wrote:
>
> > >> Are Windows users accustomed to having up-to-the-minute timezone
> > >> information? Maybe there's something I don't
Tommy wrote:
Hello,
I'm implementing a Setup Wizard to install PostgreSQL. In the documentation
it states that psql returns ZERO to the "shell" if it finished successfully.
I'm implementing a wizard in Pascal and was wondering the correct syntax to
check whether or not the shell received Z
Hello,
I'm implementing a Setup Wizard to install PostgreSQL. In the documentation
it states that psql returns ZERO to the "shell" if it finished successfully.
I'm implementing a wizard in Pascal and was wondering the correct syntax to
check whether or not the shell received ZERO?
For example,
I wrote:
> I did do some experimentation and found that among the ASCII characters
> (ie, codes 32-126), nearly all the non-C locales on my Fedora machine
> sort Z last and z next-to-last or vice versa. Most of the remainder
> sort digits last and z or Z as the last non-digit character. Since Z i
On 11/8/07, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> Andrew Dunstan wrote:
> > Tom Lane wrote:
> >> Are Windows users accustomed to having up-to-the-minute timezone
> >> information? Maybe there's something I don't know about Microsoft's
> >> update practices, but I would have thought that t
Simon Riggs wrote:
> Presumably we would not store an FSM for small tables? On the basis that
> the purpose of the FSM is to save on pointless I/O there must be a size
> of table below which an FSM is just overhead.
Hmm, do you mean that we would open and verify every page of a small
relation unt
Gregory Stark <[EMAIL PROTECTED]> writes:
> Doesn't really strike at the core reason that this is so klugy though. Surely
> the "right" thing is to push the concept of open versus closed end-points
> through deeper into the estimation logic?
No, the right thing is to take the folk who defined "dic
"Tom Lane" <[EMAIL PROTECTED]> writes:
> What I am tempted to do about this is have make_greater_string tack "zz"
> onto the supplied prefix, so that it would have to find a string that
> compares greater than "123/zz" before reporting success. This is
> getting pretty klugy though, so cc'ing to
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> The pages might well be in cache, so the file location might well be
> irrelevant from an I/O perspective. Maybe. The nth page solution allows
> the FSM block to be easily located without any FSM index, so might well
> be faster. Separate files mean more
Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
>>
>> Are Windows users accustomed to having up-to-the-minute timezone
>> information? Maybe there's something I don't know about Microsoft's
>> update practices, but I would have thought that the expectations on that
>> platform would be pretty darn l
Tom Lane wrote:
Are Windows users accustomed to having up-to-the-minute timezone
information? Maybe there's something I don't know about Microsoft's
update practices, but I would have thought that the expectations on that
platform would be pretty darn low.
No, they push updates fairly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 04 Nov 2007 18:55:59 +
Simon Riggs <[EMAIL PROTECTED]> wrote:
ve up and have ready access to
> > is a HP DL 585. It has 8 cores (Opteron), 32GB of ram and 28
> > spindles over 4 channels.
> >
> > My question is -hackers, is who wants first
On Sun, 2007-11-04 at 18:55 +, Simon Riggs wrote:
> On Fri, 2007-11-02 at 10:42 -0700, Joshua D. Drake wrote:
> >
> > My question is -hackers, is who wants first bite and what do they
> > want :)
>
> I'll take a few slots, probably 3 x 1 days, at least a week apart. Won't
> be able to start
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> For people using prebuilt packages, it's really the packager's problem.
>> I think most packagers are going to move to depending on a system
>> timezone DB if at all possible.
> Still need a solution for those where it's not possible
On Wed, 2007-11-07 at 17:18 +0100, Jacques Caron wrote:
> It is well known that in some instances the Postgresql will make
> estimates of the number of distinct values in a table that can be
> quite far off reality. This then has a tendency to make the planner
> lean towards unsavory plans (rea
On Thu, 2007-11-08 at 15:24 +, Heikki Linnakangas wrote:
> I still feel the FSM should be in a file of it's own, rather than
> distributed on every nth heap page. It makes scanning it quicker,
> because it's sequential rather than random access, we're going to need
> a
> solution for indexes
Andrew Dunstan wrote:
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Well, the state machine definitely thinks that tag names should
contain
only ASCII letters (with possibly a leading or trailing '/').
Given the
HTML examples I suppose we should allow n
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>> Zdenek Kotala wrote:
>>> I think we need some different mechanism how to deliver timezone updated.
>
>> Even when the system TZ is not used, we could deliver our "zic"
>> executable (pgzic?) and let the user drop the latest tzdata so
[ BCC to hackers.]
I have added a High Availability, Load Balancing, and Replication
Feature Matrix table to the docs:
http://momjian.us/main/writings/pgsql/sgml/high-availability.html#HIGH-AVAILABILITY-MATRIX
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
Enterpris
Brendan Jurd wrote:
> On Nov 9, 2007 3:17 AM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > We want patch submitters to spend their time on patches, not learning
> > our style. The fact is that pgindent is a silver bullet in some ways.
>
> Well there's a lot of support for the idea of pgindent bei
On Nov 9, 2007 3:17 AM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> We want patch submitters to spend their time on patches, not learning
> our style. The fact is that pgindent is a silver bullet in some ways.
Well there's a lot of support for the idea of pgindent being good
enough to establish a
"Guillaume Smet" <[EMAIL PROTECTED]> writes:
> On Nov 8, 2007 12:14 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> I've applied a patch that might help you:
>> http://archives.postgresql.org/pgsql-committers/2007-11/msg00104.php
> AFAICS, it doesn't seem to fix the problem. I just compiled
> REL8_1_ST
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> If someone submits a piece of code that's totally out of line with our
> standards, we will ask him to resubmit. This step could be avoided if
> he knew what those standards were in the first place.
True, but "make it look like what you see" is more th
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Am Mittwoch, 31. Oktober 2007 schrieb Sheikh Amjad:
>> Following test case is crashing the postgresql-8.3-beta
> Btw., I didn't forget this, but I haven't found an extended period of quiet
> time to develop a proper solution.
I fixed it a few days a
Alvaro Herrera wrote:
> > > Having said that, there are two or three tips worth knowing about
> > > pg_indent's behavior, like when and how to use dashes to prevent
> > > comment blocks from being re-flowed. But it's a short list.
>
> If someone submits a piece of code that's totally out of line
Bruce Momjian wrote:
> Tom Lane wrote:
> > "Brendan Jurd" <[EMAIL PROTECTED]> writes:
> > > If Postgres did have something akin to the Python C style guide, that
> > > would be excellent. But all we've got is a standard tabstop of four
> > > spaces and the five words "Our standard format BSD style
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Zdenek Kotala wrote:
>> I think we need some different mechanism how to deliver timezone updated.
> Even when the system TZ is not used, we could deliver our "zic"
> executable (pgzic?) and let the user drop the latest tzdata somewhere
> and recompile
Zdenek Kotala wrote:
> Devrim GÜNDÜZ napsal(a):
>> Hi,
>> ftp://elsie.nci.nih.gov/pub/tzdata2007i.tar.gz
>> Per announcement:
>> "...is now available; this reflects changes for Cuba and Syria
>> circulated earlier this week on the time zone mailing list.
>> There are no code changes, so there's no
Tom Lane wrote:
Michael Glaesemann <[EMAIL PROTECTED]> writes:
What would be the disadvantages of always doing this, i.e., just
making this part of the normal update path in the backend?
(1) cycles wasted to no purpose in the vast majority of cases.
(2) visibly inconsistent behavio
Am Mittwoch, 31. Oktober 2007 schrieb Sheikh Amjad:
> Following test case is crashing the postgresql-8.3-beta
> SELECT XMLELEMENT
> ( NAME "Program",
> XMLAGG
> ( XMLELEMENT
> ( NAME "Student", s.name::xml )
> )
> ) AS "Registe
"Bruce Momjian" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>
>> Having said that, there are two or three tips worth knowing about
>> pg_indent's behavior, like when and how to use dashes to prevent
>> comment blocks from being re-flowed. But it's a short list.
>
> Agreed, and the developer's F
I found a nice paper describing a few free space management algorithms:
M. L. McAuliffe, M. J. Carey and M. H. Solomon, Towards Effective and
Efficient Free Space Management, Proceedings of the ACM SIGMOD, Jun.
1996, pages 389--400. http://citeseer.ist.psu.edu/mcauliffe96towards.html
The basi
Tom Lane wrote:
> "Brendan Jurd" <[EMAIL PROTECTED]> writes:
> > If Postgres did have something akin to the Python C style guide, that
> > would be excellent. But all we've got is a standard tabstop of four
> > spaces and the five words "Our standard format BSD style". Don't you
> > think that co
Michael Glaesemann <[EMAIL PROTECTED]> writes:
> What would be the disadvantages of always doing this, i.e., just
> making this part of the normal update path in the backend?
(1) cycles wasted to no purpose in the vast majority of cases.
(2) visibly inconsistent behavior for apps that pay atten
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
> If Postgres did have something akin to the Python C style guide, that
> would be excellent. But all we've got is a standard tabstop of four
> spaces and the five words "Our standard format BSD style". Don't you
> think that comes across as pretty weak
Am Donnerstag, 8. November 2007 schrieb Gregory Stark:
> Shouldn't the cast be implicit anyways? What does having double precision
> operators buy us? Wouldn't it introduce ambiguities?
Unless you use --enable-integer-datetimes, interval is stored as float
internally, so historically, the selecti
> Feature freeze was six months ago, and no this wouldn't be a
> "small add" even if it was the best idea since sliced bread.
+1
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomai
"Josh Berkus" <[EMAIL PROTECTED]> writes:
> Peter Eisentraut wrote:
>> There are interval * double precision operators (both ways) but none for
>> interval * numeric. Adding this would make sense since interval is now
>> optionally stored as fixed-point internally. Any objections to adding this
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
The test lab is finally starting to come to fruition. We (the
community) have been donated hardware via MyYearbook and Hi5. It is my
understanding that we may also have some coming from HP.
Also, from Sun, and from I
Peter Eisentraut wrote:
There are interval * double precision operators (both ways) but none for
interval * numeric. Adding this would make sense since interval is now
optionally stored as fixed-point internally. Any objections to adding this
in 8.4?
+1
I've been casting to Numeric anywa
Devrim GÜNDÜZ napsal(a):
Hi,
ftp://elsie.nci.nih.gov/pub/tzdata2007i.tar.gz
Per announcement:
"...is now available; this reflects changes for Cuba and Syria
circulated earlier this week on the time zone mailing list.
There are no code changes, so there's no tzcode2007i; tzcood2007h
remains cu
On Nov 2, 2007, at 13:44 , Andrew Dunstan wrote:
Ah. Good. Thanks, that's the piece I was missing.
What would be the disadvantages of always doing this, i.e., just
making this part of the normal update path in the backend? I'd think
it should save on unnecessarily dead tuples as well.
M
Gregory Stark wrote:
> "Brendan Jurd" <[EMAIL PROTECTED]> writes:
>
> > If Postgres did have something akin to the Python C style guide, that
> > would be excellent. But all we've got is a standard tabstop of four
> > spaces and the five words "Our standard format BSD style". Don't you
> > think
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
> If Postgres did have something akin to the Python C style guide, that
> would be excellent. But all we've got is a standard tabstop of four
> spaces and the five words "Our standard format BSD style". Don't you
> think that comes across as pretty weak
Kevin Grittner wrote:
I know this issue on this thread has come up at least one or two
other times lately:
http://archives.postgresql.org/pgsql-performance/2007-08/msg00113.php
I know it's a largely independent issue, but your comment about the
API not giving access to the index tuples echoe
On Nov 8, 2007 2:49 AM, Gregory Stark <[EMAIL PROTECTED]> wrote:
>
> None of these points in here seem at all analogous to the important kind of
> style details like what Tom was pointing out about using GETARG_* at the top
> of your function to make the argument types clear.
>
I would love to see
51 matches
Mail list logo
