On Fri, Aug 11, 2006 at 12:48:27AM -0400, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Do we want to enable a ICU build option in 8.2?
>
> Uh, that wasn't seriously on the table was it? AFAIR we don't have a
> current patch (ie something that applies cleanly to HEAD or near HEA
On Aug 11, 2006, at 13:48 , Bruce Momjian wrote:
Have we made any progress on this?
I made a bit of progress but am still having issues when --enable-
integer-datetimes is not enabled. I need to spend some time with gdb
and figure out what's going on. I probably won't be able to get time
Have we made any progress on this?
---
Tom Lane wrote:
> Michael Glaesemann <[EMAIL PROTECTED]> writes:
> > ... I think this just confirms that there is some kind of rounding (or
> > lack of) in interval_div. Kind of frust
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Do we want to enable a ICU build option in 8.2?
Uh, that wasn't seriously on the table was it? AFAIR we don't have a
current patch (ie something that applies cleanly to HEAD or near HEAD)
and I have not seen any discussion about it since March or so.
I
On Aug 11, 2006, at 13:31 , Bruce Momjian wrote:
Do we want to enable a ICU build option in 8.2?
I'd like to see it as an option.
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 6: explain analyze is your friend
Do we want to enable a ICU build option in 8.2?
---
Martijn van Oosterhout wrote:
-- Start of PGP signed section.
> On Mon, Jul 03, 2006 at 12:55:18AM -0400, Tom Lane wrote:
> > Fine for you, not so fine for other people wit
Joshua D. Drake wrote:
> >
> > It seems some people like the authoritative TODO list, and others want a
> > TODO wiki that they can add stuff to without having to get community
> > buy-in. I have trouble seeing how the wiki doesn't just end up being a
> > blog of ideas, but I see no harm in it as
I have looked over this addition, and I think I finally understand it.
Given three tables, A, B, C, which join as A->B, B->C, C->A, you can
really join them as A->B->C, and A->C->B. What full disjunction does is
to perform both of those joins, and return a one row for each join. Here
is an examp
It seems some people like the authoritative TODO list, and others want a
TODO wiki that they can add stuff to without having to get community
buy-in. I have trouble seeing how the wiki doesn't just end up being a
blog of ideas, but I see no harm in it as long as it is clear the items
haven't pas
Jim Nasby wrote:
> First, +1 on Josh B.'s point about trying out Trac, since it's
> already up and running. Josh D., can you just turn that on? (BTW, is
> trac linked off http://commandprompt.com anywhere? I had to google to
> find it yesterday...)
>
> On Aug 9, 2006, at 11:34 PM, Tom Lane w
Merlin Moncure wrote:
> On 8/9/06, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > Joshua D. Drake wrote:
> > > >>
> > > >> Until you have used this, it seems strange. After you start it doesn't
> > > >> ;-)
> > > >
> > > > Sure, but with openness comes cruft, which can be a problem too. Do we
> > >
Jim Nasby wrote:
> Oh, I didn't realize there was a CVSup server. I think it'd be good
> to promote that over CVS, as it's (supposedly) much easier on the
> hosting machine.
>
> Andrew, is there a way to get the buildfarm to use cvsup instead of
> cvs? Does the script just call cvs via the shell?
>
Neil Conway wrote:
On Thu, 2006-08-10 at 17:33 -0700, Joshua D. Drake wrote:
No, like the rest of the world, Trac has moved on from CVS ;)
There is CVSTrac (www.cvstrac.org), which actually predates Trac.
However, is there a reason to use Trac beyond the fact that it is
already setup? ISTM we
On Thu, 2006-08-10 at 17:33 -0700, Joshua D. Drake wrote:
> No, like the rest of the world, Trac has moved on from CVS ;)
There is CVSTrac (www.cvstrac.org), which actually predates Trac.
However, is there a reason to use Trac beyond the fact that it is
already setup? ISTM we only need a wiki, an
Alvaro Herrera wrote:
Jim Nasby wrote:
First, +1 on Josh B.'s point about trying out Trac, since it's
already up and running. Josh D., can you just turn that on? (BTW, is
trac linked off http://commandprompt.com anywhere? I had to google to
find it yesterday...)
Oh and answer Jim's questi
Alvaro Herrera wrote:
Jim Nasby wrote:
First, +1 on Josh B.'s point about trying out Trac, since it's
already up and running. Josh D., can you just turn that on? (BTW, is
trac linked off http://commandprompt.com anywhere? I had to google to
find it yesterday...)
I just noticed that the co
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> It seems a little dangerous for a dynamic library to register an
> on_proc_exit() handler. If we ever add support for unloading a dynamic
> library, we'll have to add an unregister_on_proc_exit() too.
True, but there might be other uses for such a
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I use more or less what is in the developers' FAQ (not surprising, since
> I contributed it). It works just fine for me. See
> http://www.postgresql.org/docs/faqs.FAQ_DEV.html#item1.9
> We should probably bring the docs in line with that, unless someo
I've been reviewing Jonah's INSERT/UPDATE RETURNING patch, and I've run
into a nasty problem with UPDATEs across inheritance trees: we really
need a separate instance of the RETURNING targetlist for each child
table. Consider
CREATE TABLE p (f1 int);
CREATE TABLE c (fc int) INHERI
Jim Nasby wrote:
> First, +1 on Josh B.'s point about trying out Trac, since it's
> already up and running. Josh D., can you just turn that on? (BTW, is
> trac linked off http://commandprompt.com anywhere? I had to google to
> find it yesterday...)
I just noticed that the code repository on
> Also, should we create an on_proc_exit() handler that would unload all
> dynamic libraries (specifically to call the _PG_fini() functions)?
Yeah, I thought about that too, but I'm inclined not to do it;
it seems like just excess cycles. The process is quitting anyway,
so the only reason
First, +1 on Josh B.'s point about trying out Trac, since it's
already up and running. Josh D., can you just turn that on? (BTW, is
trac linked off http://commandprompt.com anywhere? I had to google to
find it yesterday...)
On Aug 9, 2006, at 11:34 PM, Tom Lane wrote:
Mark Kirkwood <[EMAIL
Oh, I didn't realize there was a CVSup server. I think it'd be good
to promote that over CVS, as it's (supposedly) much easier on the
hosting machine.
Andrew, is there a way to get the buildfarm to use cvsup instead of
cvs? Does the script just call cvs via the shell?
On Aug 9, 2006, at 1
On Aug 10, 2006, at 12:29 PM, alfranio correia junior wrote:
One of the great things about Oracle is that they expose a hell of
a lot
of the technology they use to build features like replication; ie:
take
a look at DBMS_*.
If I am not wrong such procedures are only for administrative purpo
On 8/9/06, Bruce Momjian <[EMAIL PROTECTED]> wrote:
Joshua D. Drake wrote:
> >>
> >> Until you have used this, it seems strange. After you start it doesn't ;-)
> >
> > Sure, but with openness comes cruft, which can be a problem too. Do we
> > want everyone's idea of a useful feature listed? I d
Merlin Moncure wrote:
what version postgresql?
8.1.4
merlin
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
--
Jeff Davis wrote:
At the link:
http://www.postgresql.org/docs/8.1/static/source.html
It gives some style configuration code to put in the .emacs file.
However, when I do that, emacs doesn't appear to follow the style of the
postgresql source. For instance, inside a function definition emacs
alw
At the link:
http://www.postgresql.org/docs/8.1/static/source.html
It gives some style configuration code to put in the .emacs file.
However, when I do that, emacs doesn't appear to follow the style of the
postgresql source. For instance, inside a function definition emacs
always indents by 8 col
Marc,
> > ... will post something to -www as
>
> soon as I have something up and running ...
Given that JD is already pulling something into a Trac instance, why don't we
just try using that? It has both an issue tracker and a wiki, and it's up
and running now. When we have a firmer idea wha
>
> Why reinvent the wheel for everything if there was an interface that
> offered some of the needed functionality? Maybe PostgreSQL-R is simply
> too deep in the database for any of this to be useful, but I'm 99%
> certain that Slony could make use of some of this stuff, such as a hook
> on tu
On Thu, Aug 10, 2006 at 12:31:52PM -0400, Tom Lane wrote:
> "Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> >> I'm leaning slightly to the fold-it-into-PQprepare way, but am by
> >> no means set on that. Comments anyone?
>
> > As a heavy user of libpq via DBD::Pg, +1 to folding in.
>
> Anoth
Gene <[EMAIL PROTECTED]> writes:
> "Your best bet might be to partition the table into two subtables, one
> with "stable" data and one with the fresh data, and transfer rows from
> one to the other once they get stable. Storage density in the "fresh"
> part would be poor, but it should be small
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> On 8/10/06, Tom Lane <[EMAIL PROTECTED]> wrote:
>> So the short answer is "get a real operating system"?
> changing a registry setting is not terrible in and of itself, akin to
> manually manipluating procfs, but the behavior is in a failure
> conditi
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
>> I'm leaning slightly to the fold-it-into-PQprepare way, but am by
>> no means set on that. Comments anyone?
> As a heavy user of libpq via DBD::Pg, +1 to folding in.
Another thought: I looked into the protocol description and was reminded
that
On 8/10/06, Tom Lane <[EMAIL PROTECTED]> wrote:
"William ZHANG" <[EMAIL PROTECTED]> writes:
> Maybe this article can help:
> Windows and the ClearCase process limit: Understanding the desktop heap
> http://www-128.ibm.com/developerworks/rational/library/05/1220_marechal/
So the short answer is "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I'm leaning slightly to the fold-it-into-PQprepare way, but am by
> no means set on that. Comments anyone?
As a heavy user of libpq via DBD::Pg, +1 to folding in.
- --
Greg Sabino Mullane [EMAIL PROTECTED] [EMAIL PROTECTED]
End Point Corporatio
On 8/10/06, William ZHANG <[EMAIL PROTECTED]> wrote:
Maybe this article can help:
Windows and the ClearCase process limit: Understanding the desktop heap
http://www-128.ibm.com/developerworks/rational/library/05/1220_marechal/
i doubled all my heap settings and was able to roughly double the
"William ZHANG" <[EMAIL PROTECTED]> writes:
> Maybe this article can help:
> Windows and the ClearCase process limit: Understanding the desktop heap
> http://www-128.ibm.com/developerworks/rational/library/05/1220_marechal/
So the short answer is "get a real operating system"?
I'm not sure I beli
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Any thoughts about where to put the call to process_backend_libraries()
> (the new function to handle backend_load_libraries)?
> I'm thinking that it should go in PostgresMain(), just after (before?)
> the call to BeginReportingGUCOptions() - by tha
As for forcing the library load to occur, I propose a new GUC variable
"backend_load_libraries" that is much like the postmaster's
preload_libraries, except that the requested library loads happen
at backend start time instead of in the postmaster. Then we need
write and document the code o
Maybe this article can help:
Windows and the ClearCase process limit: Understanding the desktop heap
http://www-128.ibm.com/developerworks/rational/library/05/1220_marechal/
""Merlin Moncure"" [EMAIL PROTECTED]
>I confirmed the problem on a fairly recent 8.2devel
>
> merlin
>
> On 8/10/06, Merlin
On 8/5/06, Tom Lane <[EMAIL PROTECTED]> wrote:
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> Here's the updated patch with DELETE RETURNING removed. This isn't
> really an issue because no one wanted DELETE RETURNING to begin with.
I don't have the time to add DELETE RETURNING back in. My i
Volkan YAZICI <[EMAIL PROTECTED]> writes:
> [ patch to add PQdescribePrepared and PQdescribePortal ]
After looking this over, I don't see the point of PQdescribePortal,
at least not without adding other functionality to libpq. There is
no functionality currently exposed by libpq that allows creat
I confirmed the problem on a fairly recent 8.2devel
merlin
On 8/10/06, Merlin Moncure <[EMAIL PROTECTED]> wrote:
what version postgresql?
merlin
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Something must be odd in your environment - we have several Windows
buildfarm members running through on CVS HEAD quite happily.
cheers
andrew
William ZHANG wrote:
I tested it on the CVS head source.
C:\> ver
Microsoft Windows XP [Version 5.1.2600]
$ uname -a
MINGW32_NT-5.1 BEAR 1.0.11(0
I tested it on the CVS head source.
C:\> ver
Microsoft Windows XP [Version 5.1.2600]
$ uname -a
MINGW32_NT-5.1 BEAR 1.0.11(0.46/3/2) 2004-04-30 18:55 i686 unknown
$ pwd
/home/uniware/pgsql/src/interfaces/ecpg/test/sql
$ make
gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline -Wdeclara
what version postgresql?
merlin
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
-Original Message-
From: "Marc G. Fournier" <[EMAIL PROTECTED]>
To: "Dave Page"
Cc: "Jim C. Nasby" <[EMAIL PROTECTED]>; "Bruce Momjian" <[EMAIL PROTECTED]>;
"Josh Berkus" ; "Christopher Browne" <[EMAIL PROTECTED]>;
"pgsql-hackers@postgresql.org"
Sent: 10/08/06 05:30
Subject: RE: [HACK
On Thu, Aug 10, 2006 at 09:20:09AM -0400, [EMAIL PROTECTED] wrote:
> Mathematically, 1.0 = 0.9500... -> 1.05000...
>
> In theory, B-Tree could be fine with this. As long as the operators
> for =, <>, <, and > are made to consistently understand this principle.
> For example:
>
> 1.0 = 0.95
>
Martijn van Oosterhout writes:
> You're not required to provide all the casts, but it's user friendly to
> do so. Requiring double casts to go between two essentially compatable
> types seems silly...
I believe what Greg had in mind included the idea that the parser would
automatically find two-s
On Wed, Aug 09, 2006 at 12:21:40PM +0100, stark wrote:
> I think the ideal combination is having every type have precisely one implicit
> cast "up" the type "tree" and assignment casts down the "tree". I don't see us
> every needing anything more complex than a flat "tree" of a single base type
> f
On Wednesday 09 August 2006 20:57, Hannu Krosing wrote:
> >
> > Why reinvent the wheel for everything if there was an interface that
> > offered some of the needed functionality? Maybe PostgreSQL-R is simply
> > too deep in the database for any of this to be useful, but I'm 99%
> > certain that Slo
Stephen Frost <[EMAIL PROTECTED]> writes:
> This was using just a straight-up 'numeric' data type though. Perhaps
> for that case we could drop the unnecessary zeros?
That would make numeric useless for the common scientific/engineering
usage where you write the number of decimal places you think
On Thu, Aug 10, 2006 at 03:40:11AM -, Andrew - Supernews wrote:
> On 2006-08-10, Stephen Frost <[EMAIL PROTECTED]> wrote:
> >> Yeah, because numeric_cmp says that 1.0 and 1.00 are equal (what else
> >> could it say? "less" and "greater" are surely wrong). So you need to
> > It could say "not
On Wed, Aug 09, 2006 at 11:35:48PM -0400, Tom Lane wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > * Tom Lane ([EMAIL PROTECTED]) wrote:
> >> Yeah, because numeric_cmp says that 1.0 and 1.00 are equal (what else
> >> could it say? "less" and "greater" are surely wrong). So you need to
> >
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Wed, 2006-08-09 at 10:04 -0400, Tom Lane wrote:
>> Another option is to have pg_current_xlog_location force a write (but
>> not fsync) as far as the Insert pointer it's about to return. This
>> would eliminate any issues about inconsistency between resu
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > Makes me curious if it really makes sense to keep trailing zeros...
>
> AFAIR we consider them mainly as a display artifact. An application
> that's declared a column as numeric(7,2) is likely to expect to see
>
Gene wrote:
You are correct the main part I'm worried about is the updates, being
so far from the originals.
Yeah, you won't benefit from the patch at all.
The reason I'm doing the clustering is I was hoping that with the
"stable" non-updating partitions I could execute a CLUSTER at night
(sl
Jonah H. Harris wrote:
On 8/9/06, Tom Lane <[EMAIL PROTECTED]> wrote:
UPDATE tries to place the new tuple on the same page it's already
on.
I think he meant for INSERT.
Right. Update is indeed taken care of already.
One example where this would help would be a customer_history table that
Tom Lane wrote:
Yeah, the main problem I have with TODO-on-a-wiki is the question of
quality control. I've been heard to complain that "the TODO list
consists of everything Bruce thinks is a good idea", but for the most
part things don't get onto TODO without some rough consensus on the
mailing
60 matches
Mail list logo
