On Thu, 27 Aug 2009, Ron Mayer wrote:
The Linux kernel seems to do fine with a "when it is ready" cycle,
where some releases(2.6.24) take twice the time of others(2.6.28)[1,2].
[2] http://fblinux.freebase.com/view/base/fblinux/views/linux_kernel_release
That link has bad data. If you check th
Itagaki Takahiro wrote:
> KaiGai Kohei wrote:
>
>> The pg_largeobject system catalog is reworked to manage its metadata.
>>
>> CATALOG(pg_largeobject,2613)
>> {
>> Oid loowner;/* OID of the owner */
>> Oid lochunk;/* OID of the data chunks */
>>
KaiGai Kohei wrote:
> The pg_largeobject system catalog is reworked to manage its metadata.
>
> CATALOG(pg_largeobject,2613)
> {
> Oid loowner;/* OID of the owner */
> Oid lochunk;/* OID of the data chunks */
> aclitem loacl[1]; /*
On Fri, Aug 28, 2009 at 4:39 AM, Ron Mayer wrote:
> Josh Berkus wrote:
>> There's some very good reasons for the health of the project to have
>> specific release dates and stick to them.
>
> Help me understand why?
>
> The Linux kernel seems to do fine with a "when it is ready" cycle,
> where some
Adriano Lange writes:
> How can I get the used memory of a memory context?
MemoryContextStats() might help. It just dumps the info to stderr
though.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscrip
The attached patch provides access control features on largeobject.
This patch adds the ownership and two permissions (SELECT and UPDATE) on
largeobjects. The two permissions controls reader and writer accesses to
the largeobejcts. Only owner can unlink the largeobject which is owned by.
It also a
Josh Berkus wrote:
> There's some very good reasons for the health of the project to have
> specific release dates and stick to them.
Help me understand why?
The Linux kernel seems to do fine with a "when it is ready" cycle,
where some releases(2.6.24) take twice the time of others(2.6.28)[1,2]
On Sun, Aug 16, 2009 at 5:31 PM, Robert Haas wrote:
> It seems that the needed checks are very similar to the ones that we
> already implement when setting restrictinfo->mergeopfamilies. That is
> filled in by get_mergejoin_opfamilies(), which checks for btree
> opfamilies where the strategy numbe
Hello,
this small patch complete MOVE support in plpgsql and equalize plpgsql
syntax with sql syntax.
There are possible new directions:
FORWARD expr, FORWARD ALL, BACKWARD expr, BACKWARD all.
These directions are not allowed for FETCH statement, because returns more rows.
This patch is relate
Andrew Dunstan wrote:
> I don't know of anyone who is likely to want to try out alphas in their
> normal development environments. The client I approached was
> specifically prepared to test beta releases that way.
Perhaps end-users won't, but I think companies who develop software that
works on t
Hi,
How can I get the used memory of a memory context?
Is there some function like:
int getMemoryUsage( MemoryContext )
?
I still working in a subplan cache for a query optimizer and I need to know
whether a temporary memory context is in certain limits.
Thanks
Adriano
--
Sent via pgsql-ha
Alvaro Herrera wrote:
> So I'm going to apply your patch to both 8.4 and HEAD; we can always
> improve it later, I guess.
Thank you for your applying.
I think the fix is ugly, too. We need to introduce cleaner solution for 8.5.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
-
On Thu, Aug 27, 2009 at 6:09 PM, Tom Lane wrote:
> "Kevin Grittner" writes:
>> Robert Haas wrote:
>>> The final CommitFest began November 11, 2008. It closed March 25,
>>> 2009 (+ 144 days). Beta1 was released April 15, 2009 (+ 21 days).
>
>> I'm not entirely clear on what was happening during
On Thu, Aug 27, 2009 at 10:17:32AM -0400, Alvaro Herrera wrote:
> Alvaro Herrera escribió:
>
> > > I initially left these exactly the same as for ASCII (the ':' and ';'
> > > usage). However, it's quite possible to make it use other characters.
> > > We could use the same lines, or two, three or
Tom Lane wrote:
> I've applied the first three of these changes, but not the last two
> (the 'dist' assignments). "clang" seems to have a tin ear for style :-(.
> It's failing to notice that we have several similar code blocks in
> sequence in these two places, and making the last one different fr
Simon,
> The level of detailed planning happening now is a change for the
> community and in general I think it's a good thing. In the past we've
> always said it will be shipped when it's ready, and now we seem to be
> caught by our own rules. There's no need to make hard decisions now.
> Let's k
Le jeudi 27 août 2009 à 14:27 -0500, Jaime Casanova a écrit :
> the point was that if we simply were saying: hey! mysql can interpret
> this, make postgres do the same then we could end up with a lot of
> broken stuff... just because mysql users think is wonderful to not
> have to write sane code..
David Fetter wrote:
How about something in the alphas to the effect of,
Using PostgreSQL?
Have a development server to spare?
Try your application stack on alpha1!
We'd love to hear back. Functionality, performance, you name it.
I don't know of anyone who is likely to
On Thu, Aug 27, 2009 at 03:04:20PM -0400, Robert Haas wrote:
> On Thu, Aug 27, 2009 at 2:54 PM, Peter Eisentraut wrote:
> > On tor, 2009-08-27 at 09:58 -0400, Robert Haas wrote:
> >> To get positive results in which you can have confidence, you
> >> have to know that the testing which was done actu
"Kevin Grittner" writes:
> Robert Haas wrote:
>> The final CommitFest began November 11, 2008. It closed March 25,
>> 2009 (+ 144 days). Beta1 was released April 15, 2009 (+ 21 days).
> I'm not entirely clear on what was happening during the 21 days
> between the end of the CommitFest and an
Kevin Grittner escribió:
> Robert Haas wrote:
>
> > The final CommitFest began November 11, 2008. It closed March 25,
> > 2009 (+ 144 days). Beta1 was released April 15, 2009 (+ 21 days).
>
> I'm not entirely clear on what was happening during the 21 days
> between the end of the CommitFest
Robert Haas escribió:
> Of course I don't think we'd actually need to start a CommitFest quite
> as quickly as we did this time, because with a shorter release cycle
> there ought to be a lot less patches already accumulated by the time
> we release, especially if there are clearly defined tasks f
t
Werner Echezuria wrote:
Hi, I need to return a set of records from a query, first I translate
from sqlf to sql and later I wanna return the query, but the server
crash (I guess it crashes around the yyparse call).
This is the sql:
CREATE OR REPLACE FUNCTION sqlf (text) RETURNS SETOF record
A
Robert Haas wrote:
> The final CommitFest began November 11, 2008. It closed March 25,
> 2009 (+ 144 days). Beta1 was released April 15, 2009 (+ 21 days).
I'm not entirely clear on what was happening during the 21 days
between the end of the CommitFest and and the release of beta1. I
seem
On Thu, Aug 27, 2009 at 04:22:58PM -0400, Jonah H. Harris wrote:
> On Thu, Aug 27, 2009 at 3:53 PM, David Fetter wrote:
>
> > > I would appreciate it if somebody could send out some messages
> > > of calm, while I/we work. The time for open review will come
> > > around soon enough.
> >
> > With
and...@dunslane.net (Andrew Dunstan) writes:
> Actually, what I had in mind was getting people to run their
> applications etc. in some non-production environment on the beta. I
> talked to a client today and he said "sure, we have several
> development environments and we can put one or two on the
On Thu, Aug 27, 2009 at 3:56 PM, Alvaro
Herrera wrote:
> Robert Haas escribió:
>> What I want to do is address the concern about too much of any given
>> year being consumed by beta and CommitFest. I'm not sure I know how
>> to do that though.
>
> How much time were we in beta? I thought most tim
On Thu, Aug 27, 2009 at 3:53 PM, David Fetter wrote:
> > I would appreciate it if somebody could send out some messages of
> > calm, while I/we work. The time for open review will come around
> > soon enough.
>
> With all due respect, the time for open review is now. You have
> already tried clo
Jan Urbański wrote:
> Patch -p1 attached.
Applied, thanks
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to
Patch -p1 attached.
Cheers,
Jan
diff --git a/doc/src/sgml/release-8.4.sgml b/doc/src/sgml/release-8.4.sgml
index 184bf47..50d9cb0 100644
--- a/doc/src/sgml/release-8.4.sgml
+++ b/doc/src/sgml/release-8.4.sgml
@@ -104,7 +104,7 @@
Properly show fractional seconds and milliseconds
Robert Haas escribió:
> What I want to do is address the concern about too much of any given
> year being consumed by beta and CommitFest. I'm not sure I know how
> to do that though.
How much time were we in beta? I thought most time was spent trying to
get to beta in the first place.
--
Alv
On Thu, Aug 27, 2009 at 08:48:43PM +0100, Simon Riggs wrote:
>
> On Sun, 2009-08-23 at 01:57 -0400, Tom Lane wrote:
> > Robert Haas writes:
> > > I posted a note about a week ago which drew far less commentary
> > > than I expected, regarding the timetable for the release of 8.5.
> >
> > > http:
On Sun, 2009-08-23 at 01:57 -0400, Tom Lane wrote:
> Robert Haas writes:
> > I posted a note about a week ago which drew far less commentary than I
> > expected, regarding the timetable for the release of 8.5.
>
> > http://archives.postgresql.org/pgsql-hackers/2009-08/msg01256.php
>
> > Perhaps
Hi,
Robert Haas writes:
> On Thu, Aug 27, 2009 at 2:54 PM, Peter Eisentraut wrote:
>> We have regression tests. They could and should be expanded. That's a
>> developer job, and we can start working on that now. But this
>> discussion was about what to do during beta. And I think during beta
2009/8/27 Rob Wultsch :
>
> And that behavior has changed to be sane in 5.0+, iirc.
>
5.0.12+ actually... that is stated in the same thread...
the point was that if we simply were saying: hey! mysql can interpret
this, make postgres do the same then we could end up with a lot of
broken stuff... j
On Thu, Aug 27, 2009 at 07:08:28PM +0100, Simon Riggs wrote:
>
> On Mon, 2009-08-17 at 11:19 +0300, Heikki Linnakangas wrote:
>
> > I think there's a race condition in the way LogCurrentRunningXacts() is
> > called at the end of checkpoint. This can happen in the master:
> >
> > 1. Checkpoint st
On Thu, Aug 27, 2009 at 2:54 PM, Peter Eisentraut wrote:
> On tor, 2009-08-27 at 09:58 -0400, Robert Haas wrote:
>> To get positive results in which you can have confidence, you have to
>> know that the testing which was done actually did a reasonably good
>> job exercising the code in a way that w
On tor, 2009-08-27 at 09:58 -0400, Robert Haas wrote:
> To get positive results in which you can have confidence, you have to
> know that the testing which was done actually did a reasonably good
> job exercising the code in a way that would have flushed out bugs, had
> any been present. That soun
Hi, I need to return a set of records from a query, first I translate
from sqlf to sql and later I wanna return the query, but the server
crash (I guess it crashes around the yyparse call).
This is the sql:
CREATE OR REPLACE FUNCTION sqlf (text) RETURNS SETOF record
AS 'MODULE_PATHNAME', 'sqlf'
L
2009/8/27 Jaime Casanova :
> 2009/8/27 Jean-Michel Pouré :
>>
>> Otherwise, replicating some MySQL SQL syntax will not work.
>>
>> As you know, people willing to use PostgreSQL replication are possibly
>> already MySQL replication users. So if they test and PostgreSQL fails,
>> this is too bad.
>>
Tom Lane wrote:
I assume you are in effect saying you don't mind if there is an
occasional blank line in the output.
What blank line? I would expect prettyprinting of expressions to
sometimes insert an embedded newline, but not one at the beginning
or end. Do you have a counterexample?
Andrew Dunstan writes:
> OK, and how are we going to set that flag? Like I did, with a separate
> function?
I would be inclined to invent a variant of pg_get_viewdef with an
additional parameter rather than choosing a new function name, but
otherwise yeah. Or we could decide this isn't worth al
On Mon, 2009-08-17 at 11:19 +0300, Heikki Linnakangas wrote:
> I think there's a race condition in the way LogCurrentRunningXacts() is
> called at the end of checkpoint. This can happen in the master:
>
> 1. Checkpoint starts
> 2. Transaction 123 begins, and does some updates
> 3. Checkpoint end
Tom Lane wrote:
Andrew Dunstan writes:
I am confused.
The original two line addition was already in effect driven by the
PRETTY_INDENT flag, because the appendContextKeyword call would be
effectively a no-op if that flag wasn't on. But apparently some people
don't want each c
Alex Hunsaker writes:
> (do you have to mark every function that calls ereport(ERROR) as one
> that exits?)
That would be an open-ended project, and probably in many cases wouldn't
change the clang report anyway. I think it's only worth worrying about
the ones that we find will suppress some fal
On Thu, Aug 27, 2009 at 06:39, Grzegorz Jaskiewicz wrote:
> heh, sorry folks for the noise again :/
>
> There was a fair amount of false positives there - due to nature of Assert()
> macro. Mainly, since assert_enabled is a runtime variable, not a macro
> (which I sadly overlooked).
>
> So, hardcod
On Thu, Aug 27, 2009 at 12:47 PM, Jeff Janes wrote:
>> -- Forwarded message --
>> From: Tom Lane
>> To: Robert Haas
>> Date: Thu, 27 Aug 2009 10:11:24 -0400
>> Subject: Re: 8.5 release timetable, again
>>
>> What I'd like to see is some sort of test mechanism for WAL recovery.
>>
Andrew Dunstan writes:
> I am confused.
> The original two line addition was already in effect driven by the
> PRETTY_INDENT flag, because the appendContextKeyword call would be
> effectively a no-op if that flag wasn't on. But apparently some people
> don't want each column on a separate lin
>
> -- Forwarded message --
> From: Tom Lane
> To: Robert Haas
> Date: Thu, 27 Aug 2009 10:11:24 -0400
> Subject: Re: 8.5 release timetable, again
>
> What I'd like to see is some sort of test mechanism for WAL recovery.
> What I've done sometimes in the past (and recently had to
2009/8/27 Jean-Michel Pouré :
>
> Otherwise, replicating some MySQL SQL syntax will not work.
>
> As you know, people willing to use PostgreSQL replication are possibly
> already MySQL replication users. So if they test and PostgreSQL fails,
> this is too bad.
>
yeah! but some times the reason MyS
Greg Stark writes:
> On Thu, Aug 27, 2009 at 3:11 PM, Tom Lane wrote:
>> ... However this is quite haphazard since (a) the regression tests
>> aren't especially designed to exercise all of the WAL logic, and (b)
>> pg_dump might not show the effects of some problems, particularly not
>> corruption
Tom Lane wrote:
Andrew Dunstan writes:
OK, drawing this together, what I did was to go back closer to my
original idea, but put this in a separate function, so nobody would get
too upset ;-)
This seems seriously ugly. Why don't you have the flag just driving
your original two-line
Andrew Dunstan writes:
> OK, drawing this together, what I did was to go back closer to my
> original idea, but put this in a separate function, so nobody would get
> too upset ;-)
This seems seriously ugly. Why don't you have the flag just driving
your original two-line addition?
Heikki Linnakangas writes:
>> *** src/Makefile.port.old2009-08-27 10:56:46.0 +0200
>> --- src/Makefile.port2009-08-27 10:56:46.0 +0200
>> ***
>> *** 11,16
>> endif
>>
>> %.so: %.o
>> !$(CC) -shared -o $@ $<
>>
>> sqlmansect = 7
>> --- 11,16
>
Jeff Janes wrote:
> But the fact that a piece of code was executed doesn't mean
> it did the right thing. If it does something subtly wrong,
> will we notice?
That's why it takes some time to fashion a decent test.
On the other hand, if code is not being exercised at at all during the
beta
>
> -- Forwarded message --
> From: "Kevin Grittner"
> To: "Robert Haas" , "Bruce Momjian" <
> br...@momjian.us>
> Date: Thu, 27 Aug 2009 09:07:05 -0500
> Subject: Re: 8.5 release timetable, again
> Robert Haas wrote:
>
> > Maybe we should be looking at an expanded test suite that
Paul Matthews writes:
> Grzegorz Jaskiewicz wonderful static checker coughed up 5 errors in
> geo_ops.c. None of them of any particular excitement or of earth
> shattering nature. A patch is attached below that should correct these.
> (The more little issue we eliminate, the more the large ones w
On Thu, Aug 27, 2009 at 10:38 AM, Greg Stark wrote:
>
> What I've been thinking of doing is having the regression suite take a
> backup after initdb and set archive mode on. when the regression suite
> finishes start the backup up and replay all the WAL.
>
> I'm not sure how to compare the database
On Thu, Aug 27, 2009 at 11:29 AM, Tom Lane wrote:
> Robert Haas writes:
>> Well, I wasn't suggesting adding a lot more testing of things that
>> we're already testing. I was assuming that we would craft the
>> additional tests to hit areas that we are not now covering well. My
>> point here is o
On Thu, Aug 27, 2009 at 11:29:42AM -0400, Tom Lane wrote:
> Robert Haas writes:
> > Well, I wasn't suggesting adding a lot more testing of things that
> > we're already testing. I was assuming that we would craft the
> > additional tests to hit areas that we are not now covering well. My
> > poi
Magnus Hagander wrote:
> 2009/8/27 Alvaro Herrera :
> > Magnus Hagander wrote:
> >
> >> It'd be kind of neat of majordomo could insert a "held for moderation
> >> at " and "released from moderation at " headers or
> >> something. Anybody know if that's possible to do?
> >
> > You'd need to get Marc
Itagaki Takahiro wrote:
>
> Here is a patch to fix a bug in handling default values in reloptions.
> This fix should be applied to HEAD and 8.4.0.
>
> I used 'magic number -1' to propagate "not-specified" information to
> autovacuum process. It might look strange because the default value is
> ou
On Thu, Aug 27, 2009 at 3:11 PM, Tom Lane wrote:
>
> Precisely...
>
> What I'd like to see is some sort of test mechanism for WAL recovery.
> What I've done sometimes in the past (and recently had to fix the tests
> to re-enable) is to kill -9 a backend immediately after running the
> regression te
2009/8/27 Alvaro Herrera :
> Magnus Hagander wrote:
>
>> It'd be kind of neat of majordomo could insert a "held for moderation
>> at " and "released from moderation at " headers or
>> something. Anybody know if that's possible to do?
>
> You'd need to get Marc to patch the Majordomo2 source code ..
Magnus Hagander wrote:
> It'd be kind of neat of majordomo could insert a "held for moderation
> at " and "released from moderation at " headers or
> something. Anybody know if that's possible to do?
You'd need to get Marc to patch the Majordomo2 source code ...
I proposed a patch months ago to h
Robert Haas writes:
> Well, I wasn't suggesting adding a lot more testing of things that
> we're already testing. I was assuming that we would craft the
> additional tests to hit areas that we are not now covering well. My
> point here is only to what Peter said upthread: we want to be able to
>
2009/8/27 Alvaro Herrera :
> Greg Stark wrote:
>> Now why did this message get delayed by 4 hours before maia-1
>> delivered it to me? That was long enough in this to completely lose
>> the thread of conversation.
>>
>> Received: from postgresql.org (mail.postgresql.org [200.46.204.86])
>> by
On Thu, Aug 27, 2009 at 10:11 AM, Tom Lane wrote:
> Robert Haas writes:
>> ... That sounds a lot like the definition of a
>> regression test suite. Of course, we have that already, but it's
>> nowhere near comprehensive. Maybe we should be looking at an expanded
>> test suite that runs on a time
Greg Stark wrote:
> Now why did this message get delayed by 4 hours before maia-1
> delivered it to me? That was long enough in this to completely lose
> the thread of conversation.
>
> Received: from postgresql.org (mail.postgresql.org [200.46.204.86])
> by maia-1.hub.org (Postfix) with ESM
--On 27. August 2009 11:34:29 +0200 Boszormenyi Zoltan
wrote:
make -C ../../../contrib/spi refint.so autoinc.so
make[3]: Entering directory
`/home/zozo/Schönig-számlák/lucent/postgresql-8.3.5/contrib/spi'
gcc -m32 -Wall -Wmissing-prototypes -Wpointer-arith -Winline
-Wdeclaration-after-state
Tom Lane wrote:
Greg Stark writes:
Incidentally I just tried
\d information_schema.views
and it *does* seem to put newlines after some of the target list
items. After each of the CASE expressions it puts a newline. So you
*already* get a mixture of some multiple items on a line
Alvaro Herrera escribió:
> > I initially left these exactly the same as for ASCII (the ':' and ';'
> > usage). However, it's quite possible to make it use other characters.
> > We could use the same lines, or two, three or four dashed lines
> > ('╎' and '╏', or ┆' and '┇' or '┊' and '┋').
>
> Th
Robert Haas writes:
> ... That sounds a lot like the definition of a
> regression test suite. Of course, we have that already, but it's
> nowhere near comprehensive. Maybe we should be looking at an expanded
> test suite that runs on a time scale of hours rather than seconds.
mysql's got one of
Le mercredi 26 août 2009 à 15:51 -0700, Josh Berkus a écrit :
> I doubt this would be an accurate description of all Drupal
> developers.
My opinion was :
Before adding replication to PostgreSQL, it would be better to support a
basic set of MySQL syntax seems relevant:
DELETE FROM table1, table
Robert Haas wrote:
> Maybe we should be looking at an expanded test suite that runs on a
> time scale of hours rather than seconds.
> if we could say that we had a regression test suite which covered X%
> of our code, and it passed on all Y platforms tested, that would
> certainly be a confide
Roger Leigh escribió:
> On Tue, Aug 25, 2009 at 10:32:50PM -0400, Alvaro Herrera wrote:
> > Roger Leigh escribió:
> >
> > > An updated copy of the patch is attached.
> >
> > Did you give expanded output a look? (\x) I find it a bit weird that
> > the first line shows a single-pixel wide line bu
On Wed, Aug 26, 2009 at 7:39 PM, Bruce Momjian wrote:
> Peter Eisentraut wrote:
>> Much of the delay and uncertainty during beta in my mind comes from the
>> situation that we wait for negative results and don't trust the release
>> until we have seen and fixed enough of them. Instead of waiting f
heh, sorry folks for the noise again :/
There was a fair amount of false positives there - due to nature of
Assert() macro. Mainly, since assert_enabled is a runtime variable,
not a macro (which I sadly overlooked).
So, hardcoding it to (1) (using CPP) removed quite few false positives.
Ne
On 27 Aug 2009, at 10:46, Paul Matthews wrote:
Grzegorz Jaskiewicz wonderful static checker coughed up 5 errors in
geo_ops.c. None of them of any particular excitement or of earth
shattering nature. A patch is attached below that should correct
these.
(The more little issue we eliminate, the
On 24 Aug 2009, at 14:40, Peter Eisentraut wrote:
On mån, 2009-08-24 at 00:42 +0100, Grzegorz Jaskiewicz wrote:
--enable-cassert, enabled, and also added exit_* in pg_dump to list
of functions that never return.
A few more functions to mark noreturn: DateTimeParseError(), and
die_horribly()
Heikki Linnakangas írta:
> Boszormenyi Zoltan wrote:
>
>> we have come across a problem in 8.3.x (8.3.5 and 8.3.7 was tested)
>> while building PostgreSQL for 32-bit on 64-bit RHEL5 and Fedora 9.
>>
>> The following defines were used before running configure:
>>
>> export CFLAGS="-m32"
>> export
On Tue, Aug 25, 2009 at 10:32:50PM -0400, Alvaro Herrera wrote:
> Roger Leigh escribió:
>
> > An updated copy of the patch is attached.
>
> Did you give expanded output a look? (\x) I find it a bit weird that
> the first line shows a single-pixel wide line but the subsequent ones
> are thicker.
Boszormenyi Zoltan wrote:
> we have come across a problem in 8.3.x (8.3.5 and 8.3.7 was tested)
> while building PostgreSQL for 32-bit on 64-bit RHEL5 and Fedora 9.
>
> The following defines were used before running configure:
>
> export CFLAGS="-m32"
> export LD="ld -melf_i386"
>
> The above ar
Tom Lane írta:
> Greg Stark writes:
>
>> Actually it always bothered me that we don't have implicit casts from
>> integer->boolean. I can't see any ambiguity or unintentional effects
>> this would cause problems with. Am I missing something?
>>
>
> Personally, as an old Pascal-lover, I alw
Dear all,
Just a quick message about postgresql.conf auto-configuration.
When MySQL users test PostgreSQL, they load their data and run simple
SQL queries. If postgresql.conf is configured with default values, it
may produce slow results.
Would there be a way for postgresql.conf to auto configu
Grzegorz Jaskiewicz wonderful static checker coughed up 5 errors in
geo_ops.c. None of them of any particular excitement or of earth
shattering nature. A patch is attached below that should correct these.
(The more little issue we eliminate, the more the large ones will stand
out.)
At line 3131 v
Hi,
we have come across a problem in 8.3.x (8.3.5 and 8.3.7 was tested)
while building PostgreSQL for 32-bit on 64-bit RHEL5 and Fedora 9.
The following defines were used before running configure:
export CFLAGS="-m32"
export LD="ld -melf_i386"
The above are needed because when SUBSYS.o files ar
Tom Lane wrote:
Greg Stark writes:
Actually it always bothered me that we don't have implicit casts from
integer->boolean. I can't see any ambiguity or unintentional effects
this would cause problems with. Am I missing something?
Personally, as an old Pascal-lover, I always thought that C's f
88 matches
Mail list logo
