Gregory Stark writes:
> Tom Lane <[EMAIL PROTECTED]> writes:
> >
> > There isn't if you want the type to also handle long strings.
> > But what if we restrict it to short strings? See my
> message just now.
>
> Then it seems like it imposes a pretty hefty burden on the user.
>
But there are a
Theo Schlossnagle <[EMAIL PROTECTED]> writes:
> I've tracked the problem I mentioned earlier with my 4.5 million node linked
> list of s->childXids down. We use plperl to connect to Oracle over DBI. The
> select function is dbi-link's remote_select. remote_select will perform the
> query and
On Fri, 15 Sep 2006, Dave Page wrote:
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of
> > Ricardo Malafaia
> > Sent: 15 September 2006 16:35
> > To: Andrew Dunstan
> > Cc: pgsql-hackers@postgresql.org
> > Subject: Re: [HACKERS] polite request ab
I've tracked the problem I mentioned earlier with my 4.5 million node
linked list of s->childXids down. We use plperl to connect to Oracle
over DBI. The select function is dbi-link's remote_select.
remote_select will perform the query and then for each row
return_next which calls the SPI
Tom Lane <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> Tom said he didn't think there was enough code space and my own
>> experimentation was slowly leading me to agree, sadly.
>
> There isn't if you want the type to also handle long strings.
> But what if we restrict
Tom Lane wrote:
> [EMAIL PROTECTED] (Peter Eisentraut) writes:
> > sslinfo contrib module - information about current SSL certificate
> > Author: Victor Wagner <[EMAIL PROTECTED]>
>
> It was premature to add this: Bruce is still trying to get a copyright
> assignment out of the author.
Test of wr
OK, I just emailed the long subject line to my gmail account, and got
the full text:
Re: [COMMITTERS] pgsql: sslinfo contrib module - information about current SSL
Interestingly, I looked at a copy of the email I sent to start the
truncated subject thread and see in my saved mbox file:
Tom Lane wrote:
> [EMAIL PROTECTED] (Peter Eisentraut) writes:
> > sslinfo contrib module - information about current SSL certificate
> > Author: Victor Wagner <[EMAIL PROTECTED]>
>
> It was premature to add this: Bruce is still trying to get a copyright
> assignment out of the author.
Test of wr
Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Tom Lane wrote:
> > > Fixed --- I noticed it about the same time you did. I'm surprised
> > > Peter didn't get a Makefile right the first time though ...
> >
> > I'm surprised how crazy the contrib makefiles got while I wasn't
> > looking. :) I
Peter Eisentraut wrote:
> Tom Lane wrote:
> > Fixed --- I noticed it about the same time you did. I'm surprised
> > Peter didn't get a Makefile right the first time though ...
>
> I'm surprised how crazy the contrib makefiles got while I wasn't
> looking. :) I was glad to get something working
On Fri, Sep 15, 2006 at 10:06:16PM +0100, Gregory Stark wrote:
> > I'm curious, as I may be such an offender. What alternatives exist?
> > ...
> > What alternatives to limit/offset exist? If there are thousands or
> > more results, I have trouble with an idea that the entire results
> > should be q
Peter Eisentraut wrote:
> Gregory Stark wrote:
> > I don't know if this changes the calculus but apparently we've
> > already decided to go down the route of having Emacs local variables
> > attached to every file in the source directory. We have things like
> > this there:
>
> I delete them from
Tom Lane wrote:
> "Guillaume Smet" <[EMAIL PROTECTED]> writes:
> > If we consider that the prepare and the bind operations are important
> > (and I agree they can be), I wonder why do we remove the output we
> > have when log_min_duration_statement is set to 0 (I'm thinking of the
> > parse: and bi
Gregory Stark wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
>
> > Oh, OK, I had high byte meaning no header
>
> Just how annoying would it be if I pointed out I suggested precisely this a
> few days ago?
>
> Tom said he didn't think there was enough code space and my own
> experimentation w
Gregory Stark <[EMAIL PROTECTED]> writes:
> Tom said he didn't think there was enough code space and my own
> experimentation was slowly leading me to agree, sadly.
There isn't if you want the type to also handle long strings.
But what if we restrict it to short strings? See my message
just now.
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Oh, OK, I had high byte meaning no header, but clear is better, so
> 0001 is 0x01, and is "". But I see now that bytea does
> store nulls, so yea, we would be better using 1001, and it is the
> same size as .
I'm liking this ide
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Oh, OK, I had high byte meaning no header
Just how annoying would it be if I pointed out I suggested precisely this a
few days ago?
Tom said he didn't think there was enough code space and my own
experimentation was slowly leading me to agree, sadly. I
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> No, it'll be a 1-byte header with length indicating that no bytes
> >> follow,
>
> > Well, in my idea, 1001 would be 0x01. I was going to use the
> > remaining 7 bits for the 7-bit ascii value.
>
> Huh? I t
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> No, it'll be a 1-byte header with length indicating that no bytes
>> follow,
> Well, in my idea, 1001 would be 0x01. I was going to use the
> remaining 7 bits for the 7-bit ascii value.
Huh? I thought you said 0001 would be
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > FYI, we also need to figure out how to store a zero-length string. That
> > will probably be high-bit, and then all zero bits. We don't store a
> > zero-byte in strings, so that should be unique for "".
>
> No, it'll be a 1-byte hea
Bruce Momjian <[EMAIL PROTECTED]> writes:
> FYI, we also need to figure out how to store a zero-length string. That
> will probably be high-bit, and then all zero bits. We don't store a
> zero-byte in strings, so that should be unique for "".
No, it'll be a 1-byte header with length indicating t
Gregory Stark wrote:
> Case 2) Data types that are different sizes depending on the typmod but are
> always
>the same size that can be determined statically for a given typmod. In the
>case of a ASCII encoded database CHAR(n) fits this category and in any case
>we'll eventually have pe
"Guillaume Smet" <[EMAIL PROTECTED]> writes:
> If we consider that the prepare and the bind operations are important
> (and I agree they can be), I wonder why do we remove the output we
> have when log_min_duration_statement is set to 0 (I'm thinking of the
> parse: and bind: lines)?
Well, we remo
Thank you.
On Fri, 2006-09-15 at 17:41 -0400, Alvaro Herrera wrote:
> Gevik Babakhani wrote:
> > Folks,
> >
> > Could someone please provide information about how to create a correct
> > regression test?
>
> Some information you can find on the PGXS docs:
>
>
> The scripts listed in the
Gregory Stark wrote:
Case 2) Solving this is quite difficult without introducing major performance
problems or security holes. The one approach we have that's practical right
now is introducing special data types such as the oft-mentioned "char" data
type. "char" doesn't have quite
On 9/16/06, Tom Lane <[EMAIL PROTECTED]> wrote:
Well, considering that the parse and bind may take longer than the
execute, I hardly think we want to ignore them for log_duration
purposes. And we agreed that if log_duration is on and
log_min_duration_statement is not triggered, log_duration shou
Gevik Babakhani wrote:
> Folks,
>
> Could someone please provide information about how to create a correct
> regression test?
Some information you can find on the PGXS docs:
The scripts listed in the REGRESS variable are used for
regression testing of your module, just like make
"Guillaume Smet" <[EMAIL PROTECTED]> writes:
> Is it normal that when I set log_duration to on and log_statement to
> all, I have the following output when I prepare/bind/execute a
> prepared statement using the protocol:
> LOG: duration: 0.250 ms
> LOG: duration: 0.057 ms
> LOG: execute my_quer
On 9/8/06, Tom Lane <[EMAIL PROTECTED]> wrote:
It's done already ...
(Working on implementing the last changes you made in formatting in pgFouine)
Is it normal that when I set log_duration to on and log_statement to
all, I have the following output when I prepare/bind/execute a
prepared statem
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> What became of my objection that the test should be on USAGE privilege
>> for the containing schema instead?
> Was this addressed?
Yes, we arrived at this:
http://archives.postgresql.org/pgsql-committers/2006-09/msg00252.php
which doe
"Rocco Altier" <[EMAIL PROTECTED]> writes:
> With the patch attached this time...
The proposed patch to Makefile.shlib makes me gag :-( ... lying to make
about what's the purpose of a rule is seldom a good idea. Please try
as attached instead. Also, I am *really* dubious about the change to
ecpg
Tom Lane wrote:
> [EMAIL PROTECTED] (Bruce Momjian) writes:
> > Sequences were not being shown due to the use of lowercase 's' instead
> > of 'S', and the views were not checking for table visibility with
> > regards to temporary tables and sequences.
>
> What became of my objection that the test
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I don't know if this is the same thing you are talking about, but Oleg
> talked to me on the conference about "partial sort", which AFAICS it's
> about the same thing you are talking about. I think Teodor submitted a
> patch to implement it, which was
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > I have completed my first pass over the release notes and Tom has made
> > some additions:
> >
> > http://momjian.postgresql.org/cgi-bin/pgrelease
> >
> > I will probably go over them again in a few hours, update them to
> > current CVS, then m
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> Here's a patch that updates the msvc build system. It contains the
> changes in Hiroshi-sans patch from about a week ago, so please apply
> this patch instead to avoid conflicts. Changes summary:
Applied, thanks.
regards, tom
Bruce Momjian wrote:
> I have completed my first pass over the release notes and Tom has made
> some additions:
>
> http://momjian.postgresql.org/cgi-bin/pgrelease
>
> I will probably go over them again in a few hours, update them to
> current CVS, then move them into our SGML documentation
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> This patch fixes a couple of cases where we use strcasecmp() instead of
> pg_strcasecmp() in fe_connect.c, coming from the LDAP client pathc.
Applied. I found another instance in contrib/hstore, too. There are
also some occurrences in pgbench.c, bu
Folks,
Could someone please provide information about how to create a correct
regression test?
Regards,
Gevik.
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> This patch changes the function definition for ldap_start_tls_sA() on
> win32 by removing the WINLDAPAPI.
Applied.
regards, tom lane
---(end of broadcast)---
TIP 4: Have you se
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> Seems __vc_errcode was used during Visual C++ beta at some point, and is
> now declared deprecated in the system headers. This patch renames our
> use of it to __msvc_errcode, so we don't conflict anymore.
If we need this change in plpython, why not
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> This patch adds a required include file to regress.c, required to get at
> InvalidTransactionId.
If that's needed, why isn't everybody else's build falling over too?
regards, tom lane
---(end of broad
Fixed.
---
Guillaume Smet wrote:
> On 9/15/06, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > I have completed my first pass over the release notes and Tom has made
> > some additions:
> >
> > http://momjian.postgresql
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> This patch doesn't seem to cope with cases where the supplied tuple has
>> the wrong number of columns, and it doesn't look like it's being
careful
>> about dropped columns either. Also, that's a mighty bizarre-looking
>> choice of cache memory
[EMAIL PROTECTED] writes:
> On Fri, Sep 15, 2006 at 08:22:50PM +0100, Gregory Stark wrote:
>
> I'm curious, as I may be such an offender. What alternatives exist?
>
> I think you mean the concept of showing a page of information that
> you can navigate forwards and backwards a page, or select a r
On 9/15/06, Bruce Momjian <[EMAIL PROTECTED]> wrote:
I have completed my first pass over the release notes and Tom has made
some additions:
http://momjian.postgresql.org/cgi-bin/pgrelease
In Server changes, the two first lines are:
# Improve performance of statistics monitoring, espec
OK, patch sent to the 8.3 hold queue for later work, open item removed.
---
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > That does not mean that the patch is bad, and I certainly support the
> > featur
On Fri, Sep 15, 2006 at 08:22:50PM +0100, Gregory Stark wrote:
> But just in case it's not clear for anyone the usual use case for
> this paging results on a web page. As much as I normally try to
> convince people they don't want to do it that way they usually do
> end up with it implemented using
I would like to see some comments about AIX linking so we don't need to
relearn this in 1-2 years.
---
Rocco Altier wrote:
> With the patch attached this time...
>
> -rocco
>
> > -Original Message-
> > From:
I have completed my first pass over the release notes and Tom has made
some additions:
http://momjian.postgresql.org/cgi-bin/pgrelease
I will probably go over them again in a few hours, update them to
current CVS, then move them into our SGML documentation by Monday.
--
Bruce Momjian
Martijn van Oosterhout writes:
> On Fri, Sep 15, 2006 at 05:30:27PM +0100, Gregory Stark wrote:
>> Also, because heap sort is slower than qsort (on average anyways) it makes
>> sense to not bother with the heap until the number of tuples grows well
>> beyond
>> the limit or until it would other
Tom Lane wrote:
> Neil Conway <[EMAIL PROTECTED]> writes:
> > Bruce Momjian wrote:
> >> How is maintaining another file on every commit going to go over?
>
> > Well, it would clearly not be on every commit: most commits don't
> > warrant a mention in the release notes. If committers think that th
Gregory Stark wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
>
> > I believe a better way to think about this would be as an aggregate that
> > remembers the top N rows.
>
> Wouldn't such a thing just be a reimplementation of a tuplestore though? I
> mean, it's storing tuples you feed it, sortin
Tom Lane <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>
>> I think this is pretty important to cover at some point because really _not_
>> doing this just wrong.
>
> I can't get all *that* excited about it, since an index solves the
> problem.
Well I'm not all *that* ex
On Fri, Sep 15, 2006 at 05:30:27PM +0100, Gregory Stark wrote:
> Also, because heap sort is slower than qsort (on average anyways) it makes
> sense to not bother with the heap until the number of tuples grows well beyond
> the limit or until it would otherwise spill to disk.
The thought that comes
Tom Lane <[EMAIL PROTECTED]> writes:
> I believe a better way to think about this would be as an aggregate that
> remembers the top N rows.
Wouldn't such a thing just be a reimplementation of a tuplestore though? I
mean, it's storing tuples you feed it, sorting them, and spitting them back
out
On Fri, Sep 15, 2006 at 06:50:37PM +0100, Gregory Stark wrote:
> With a CHAR(1) and CASH style numeric substitute we won't have 25-100%
> performance lost on the things that would fit in 1-4 bytes. And with the
> variable sized varlena header we'll limit to 25% at worst and 1-2% usually the
> perfo
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> That does not mean that the patch is bad, and I certainly support the
> feature change. But I can't efficiently review the patch. If someone
> else wants to do it, go ahead.
I've finally taken a close look at this patch, and I don't like it any
mo
With the patch attached this time...
-rocco
> -Original Message-
> From: Rocco Altier
> Sent: Friday, September 15, 2006 2:04 PM
> To: Rocco Altier; 'Tom Lane'; 'Albe Laurenz'
> Cc: 'pgsql-hackers@postgresql.org'
> Subject: RE: [PATCHES] [HACKERS] Linking on AIX (Was: Fix
> link
> > From: Tom Lane [mailto:[EMAIL PROTECTED]
> > Mmm ... what of "make check"'s temporary installation? We need
> > to have the executables search in the temporary install's libdir,
> > *before* looking in the configured --libdir (which could easily
> > contain an incompatible back-version libpq
Following up on the recent discussion on list about wasted space in data
representations I want to summarise what we found and make some proposals:
As I see it there are two cases:
Case 1) Data types that are variable length but often quite small. This includes
things like NUMERIC which in c
Gevik Babakhani wrote:
I would like to create some regression tests for the uuid datatype.
Should those also be included in the patch to review or the regression
tests are done by the commiters?
In the patch.
cheers
andrew
---(end of broadcast)
I would like to create some regression tests for the uuid datatype.
Should those also be included in the patch to review or the regression
tests are done by the commiters?
Regards,
Gevik.
---(end of broadcast)---
TIP 6: explain analyze is your frie
"Nikolay Samokhvalov" <[EMAIL PROTECTED]> writes:
> On 8/26/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
>> "Valid" and "well-formed" have very specific distinct meanings in XML.
>> (Note that "check" doesn't have any meaning there.) We will eventually
>> want a method to verify both the validi
Tom Lane wrote:
(unless we want to invent aggregates that can return SETOF?)
Doesn't sound like a bad idea at all ...
cheers
andrew
---(end of broadcast)---
TIP 6: explain analyze is your friend
Abhijit Menon-Sen <[EMAIL PROTECTED]> writes:
> At 2006-09-05 16:35:49 -0400, [EMAIL PROTECTED] wrote:
>> So basically I don't see the point of investing effort in a
>> bug-compatible version of userlocks, when we can have something
>> cleaner and suitable for the long run with not very much more
>
Gregory Stark <[EMAIL PROTECTED]> writes:
> I've been looking at doing the following TODO item:
> Allow ORDER BY ... LIMIT # to select high/low value without sort or index
> using a sequential scan for highest/lowest values
> I think this is pretty important to cover at some point because
On Fri, 15 Sep 2006 16:15:04 -
Andrew - Supernews <[EMAIL PROTECTED]> wrote:
> On 2006-09-15, "D'Arcy J.M. Cain" wrote:
> >> Seems? Have you benchmarked it?
> >
> > Not rigourously but a few "ANALYZE EXPLAIN" statements bear out this
> > observation.
>
> The overhead of EXPLAIN ANALYZE is so
Ricardo Malafaia wrote:
> On 9/15/06, Douglas McNaught <[EMAIL PROTECTED]> wrote:
> >> What happens then when it sees something like a double variable
> >> interpolation as in $$foobar? ;)
> >
> >Then you use $FOO$ (or something else that doesn't appear in your
> >code) as the delimiter--you're not
Ricardo Malafaia wrote:
And the $$ is indeed needed for allowing languages with different
syntaxes. agreed. However, Tom, i could counter example your plperl
example:
realize that qq/end/ does not represent a matching "end"?
What happens then when it sees something like a double variable
i
On 9/15/06, Douglas McNaught <[EMAIL PROTECTED]> wrote:
> What happens then when it sees something like a double variable
> interpolation as in $$foobar? ;)
Then you use $FOO$ (or something else that doesn't appear in your
code) as the delimiter--you're not limited to just $$.
clever. still,
Hello,
Yeah, this is a cross post and it is slightly off topic but IMHO this is
important.
Tomorrow one of our own, Devrim Gunduz is becoming a man. He is sucking
it up, and committing to the cvs repo of project marriage.
May the patches reviewers be kind to him!
Congratz Devrim, have a go
On Fri, 15 Sep 2006 16:15:24 -
Andrew - Supernews <[EMAIL PROTECTED]> wrote:
> On 2006-09-15, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> > Andrew - Supernews wrote:
> >> Numbers from an actual benchmark:
> >>
> >> int4out(0) - 0.42us/call
> >> numeric_out(0) - 0.32us/call
> >>
> >> int4o
"Ricardo Malafaia" <[EMAIL PROTECTED]> writes:
> What happens then when it sees something like a double variable
> interpolation as in $$foobar? ;)
Then you use $FOO$ (or something else that doesn't appear in your
code) as the delimiter--you're not limited to just $$.
-Doug
I've been looking at doing the following TODO item:
Allow ORDER BY ... LIMIT # to select high/low value without sort or index
using a sequential scan for highest/lowest values
Right now, if no index exists, ORDER BY ... LIMIT # requires we sort all
values to return the high/low v
-- Forwarded message --
From: Ricardo Malafaia <[EMAIL PROTECTED]>
Date: Sep 15, 2006 1:28 PM
Subject: Re: [HACKERS] polite request about syntax
To: Tom Lane <[EMAIL PROTECTED]>
ok, guys. i guess i was a bit unfair. Timestamp is used everywhere
indeed, Oracle, Firebird you name
On 2006-09-15, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews wrote:
>> Numbers from an actual benchmark:
>>
>> int4out(0) - 0.42us/call
>> numeric_out(0) - 0.32us/call
>>
>> int4out(10) - 0.67us/call
>> numeric_out(10) - 0.42us/call
>
> Is this really int4
On 2006-09-15, "D'Arcy J.M. Cain" wrote:
>> Seems? Have you benchmarked it?
>
> Not rigourously but a few "ANALYZE EXPLAIN" statements bear out this
> observation.
The overhead of EXPLAIN ANALYZE is so large that it completely swamps any
real difference.
>> The point is that bigint is _not_ fast
Gregory Stark <[EMAIL PROTECTED]> writes:
> I'm reading the code in tqual.c and find that this comment doesn't seem to
> match the code. CommandId always seems to be compared with >= or <= rather
> than equality as the comment says.
Yeah, you're right, the comment seems to be written on the assump
Andrew - Supernews wrote:
> Numbers from an actual benchmark:
>
> int4out(0) - 0.42us/call
> numeric_out(0) - 0.32us/call
>
> int4out(10) - 0.67us/call
> numeric_out(10) - 0.42us/call
Is this really int4out, or is it int8out?
--
Alvaro Herrera
"Ricardo Malafaia" <[EMAIL PROTECTED]> writes:
> my complaint is that, like i said, "timestamp with time zone" is no
> good substitute for a simple "datetime". Here, someone suggested a
> CREATE DOMAIN to create an alias for it. Why isn't it provided there
> out-of-the-box by default? So you hav
The only person in denial is you. Here's a hard lesson about open
source: bitching gets you nothing.
YOU are not going to be taken seriously while all you do is complain.
And if you must complain, make sure the politeness is in the words, not
just the subject.
The only place timestamp is m
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Ricardo Malafaia
> Sent: 15 September 2006 16:35
> To: Andrew Dunstan
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] polite request about syntax
>
> my complaint is that, like i said
Sweet! I'll try it as soon as it's available.Xiaofeng Zhaohttp://www.xzing.orgerrare humanum est> Subject: Re: [HACKERS] Build v8.1.4 with VC++ 2005> Date: Fri, 15 Sep 2006 10:59:03 +0200> From: [EMAIL PROTECTED]> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]> CC: pgsql-hackers@postgresql.org> > >> I
On Fri, Sep 15, 2006 at 12:35:03PM -0300, Ricardo Malafaia wrote:
> On 9/15/06, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
> >Where is the mention of either of these on the CREATE FUNCTION page?
>
> http://www.postgresql.org/docs/8.1/interactive/sql-createfunction.html
Err, in the example? So you'
On Fri, 15 Sep 2006 15:14:10 -
Andrew - Supernews <[EMAIL PROTECTED]> wrote:
> On 2006-09-15, "D'Arcy J.M. Cain" wrote:
> > On Fri, 15 Sep 2006 10:17:55 -
> > Andrew - Supernews <[EMAIL PROTECTED]> wrote:
> >> Presumably the same speed as bigint, which is to say that while it is
> >> faste
I'm reading the code in tqual.c and find that this comment doesn't seem to
match the code. CommandId always seems to be compared with >= or <= rather
than equality as the comment says.
I'm not even sure I have these operators right as the expression as written
here is in a few places the convers
well, ain't that surprising to see so many open-source developers
living in denial and sugestions to RTFM rather than actually coping
wth the problem? are you to be taken seriously?
As a C programmer, I'm in the same league as most of you guys, so
while i can really contribute code and my talk i
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> "Albe Laurenz" <[EMAIL PROTECTED]> writes:
> > Up to now you have built against the static libpq.a
> > I didn't add the right -blibpath to this patch that
> > failed for you - the broken initdb is dynamically linked
> > but does not know where to look f
"Albe Laurenz" <[EMAIL PROTECTED]> writes:
> Up to now you have built against the static libpq.a
> I didn't add the right -blibpath to this patch that
> failed for you - the broken initdb is dynamically linked
> but does not know where to look for its shared library.
> The patch I just submitted t
On 2006-09-15, "D'Arcy J.M. Cain" wrote:
> On Fri, 15 Sep 2006 10:17:55 -
> Andrew - Supernews <[EMAIL PROTECTED]> wrote:
>> Presumably the same speed as bigint, which is to say that while it is
>> faster than numeric for calculation, it is (much) slower for input/output.
>> (The difference in
Rocco Altier wrote:
> Here is the working one:
> initdb needs:
> /usr/lib/libc.a(shr.o)
> /unix
> /usr/lib/libcrypt.a(shr.o)
>
> Here is the broken one:
> initdb needs:
> ../../../src/interfaces/libpq/libpq.so
> /usr/lib/libc.a(shr.o)
> /usr/li
On Thu, 14 Sep 2006 14:12:30 -0400
AgentM <[EMAIL PROTECTED]> wrote:
> If you force the locale into the money type, then the entire column
> must be of the same currency. That seems like an unnecessary
> limitation. Does your type support banker's rounding?
The whole point of money is to have
On Fri, 15 Sep 2006 10:17:55 -
Andrew - Supernews <[EMAIL PROTECTED]> wrote:
> Presumably the same speed as bigint, which is to say that while it is
> faster than numeric for calculation, it is (much) slower for input/output.
> (The difference in speed between bigint output and numeric output i
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> This patch doesn't seem to cope with cases where the supplied tuple has
>> the wrong number of columns, and it doesn't look like it's being careful
>> about dropped columns either. Also, that's a mighty bizarre-looking
>> choice of cache memory contex
> I suspect that up to now the buildfarm had a static build of
> PostgreSQL. What is the output of 'ldd initdb' when it builds
> and runs correctly?
>
> Is libpq.so in a non-standard directory? If yes, one either
> has to export LIBPATH in the environment or link with
> -L/location/of/libpq for th
Gregory Stark <[EMAIL PROTECTED]> writes:
> Well we could make it "edit release.txt" which someone will fix up and turn
> into release.sgml later instead.
> I think if you put a big enough separator between entries, say two black
> lines, two dashes, and two more blank lines, it wouldn't even caus
Ricardo Malafaia wrote:
I've send the comment below to the documentation page about CREATE
FUNCTION, but it got (rightfully) rejected, since it doesn't really
add up to the discussion and is more of a request about syntax. So,
here it goes:
Sorry, but "datetime" vs "timestamp with time zone"?!
"Ricardo Malafaia" <[EMAIL PROTECTED]> writes:
> Sorry, but "datetime" vs "timestamp with time zone"?! And what about
> the whole function text between $$'s? Yes, better than the '' of some
> time ago, since we don't have to put string literals in the function
> text between 's! still...
"ti
Tom Lane <[EMAIL PROTECTED]> writes:
> Well, I'm willing to (and I think usually have) put release-note-grade
> descriptions into commit log messages, but I'm not willing to add "edit
> release.sgml" to the already long process, for two basic reasons:
>
> * it'd make release.sgml into a commit bo
Please, take this as constructive criticism, since i'm a proud
open-source supporter... i would gladly use PostgreSQL at work,
clunkier syntax or not, but it's otherwise difficult to sell it to my
Windows-minded coworkers...
I would love to take this as constructive criticism, but you haven't
1 - 100 of 127 matches
Mail list logo
