Stephan Szabo <[EMAIL PROTECTED]> writes:
> I'd thought there was still a question of where such a thing would live?
> If it's an external project or a contrib thing, the above might be true,
> but if it's meant to be a truly supported internal builtin then the
> function call cost is part of the
On Sun, 26 Sep 2004, Tom Lane wrote:
> > Wouldn't pg 8.0 be a good release to get rid of the type Money?
>
> (1) there is not actually consensus to get rid of it.
The doc seems to be clear about it.
What does it provide that numeric doesn't? The only extra thing I know is
a currency symbol that
"Ross J. Reedstrom" <[EMAIL PROTECTED]> writes:
> ... So, all this append-only writing leads to files with lots of dead
> tuples, so the vacuum command was added to reclaim space.
Actually, I believe the original Postgres design envisioned that no
tuple would ever be permanently deleted: the idea
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> Wouldn't pg 8.0 be a good release to get rid of the type Money?
No.
(1) there is not actually consensus to get rid of it.
(2) we are already long past the point where we will force initdb
for noncritical problems. The right time to propose this wou
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I am confused. I just checked my backend binary and I don't see any
> unusual libs required:
> $ ldd postgres
> libz.so => /usr/lib/libz.so (0x2833f000)
> libncurses.so.5 => /shlib/libncurses.so.5 (0x2834e000)
I do not believe eit
Wouldn't pg 8.0 be a good release to get rid of the type Money?
Maybe there is also other deprecated things that are suitable to get rid
of in a .0 release.
--
/Dennis Björklund
---(end of broadcast)---
TIP 2: you can get off all lists at once wi
On Sat, 25 Sep 2004, Bruce Momjian wrote:
> I am confused. I just checked my backend binary and I don't see any
> unusual libs required:
>
> $ ldd postgres
> libz.so => /usr/lib/libz.so (0x2833f000)
> libncurses.so.5 => /shlib/libncurses.so.5 (0x2834e000)
> libdl.so
On Sat, 25 Sep 2004, Greg Stark wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
>
> > But shouldn't the comparison be against sorting on col not lower(col)?
> > strxfrm(col) sorts seem comparable to col, strxfrm(lower(col)) sorts seem
> > comparable to lower(col). Some collations do treat 'A'
On Sat, Sep 25, 2004 at 11:14:53AM +0100, Simon Riggs wrote:
> >Jim C. Nasby
>
> Fair questions. MVCC has been tightly locked into Postgres/SQL for the whole
> of its history. There is much written on this and you should search some
> more - references are in the manual.
Well, not quite it's whol
Stephan Szabo <[EMAIL PROTECTED]> writes:
> But shouldn't the comparison be against sorting on col not lower(col)?
> strxfrm(col) sorts seem comparable to col, strxfrm(lower(col)) sorts seem
> comparable to lower(col). Some collations do treat 'A' and 'a' as be
> adjacent in sort order, but that's
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
---
Da
I am confused. I just checked my backend binary and I don't see any
unusual libs required:
$ ldd postgres
libz.so => /usr/lib/libz.so (0x2833f000)
libncurses.so.5 => /shlib/libncurses.so.5 (0x2834e000)
libdl.so => /shlib/libdl.so (0x2838c000)
libm.so => /s
I wrote:
> My present theory about the cause is that the backend lost its CPU
> quantum immediately after doing the send() that responded to the last
> INSERT, and was interrupted by SIGQUIT before it could continue.
> If you look at pq_flush() you'll see that it does not reset
> PqSendPointer unti
[EMAIL PROTECTED] wrote:
If the memset
bypasses the cache then the following access will cause a cache line
miss, which can be so slow that using the faster memset can result in a
net performance loss.
Could you suggest some structs to test? If I get your meaning, I would make a loop that
Jan Wieck <[EMAIL PROTECTED]> writes:
> On 9/24/2004 10:24 PM, Tom Lane wrote:
>> If you can actually prove that a *different session* was able to see as
>> committed data that was not safely committed, then we have another
>> problem to look for. I am hoping we have only one nasty bug today ;-)
On Sat, 25 Sep 2004, Joe Conway wrote:
Andrew Dunstan wrote:
In postgres.cvsup:
# complete distribution, including all below
pgsql
earthdistance
I've been using this in postgres.cvsup
# complete distribution, including all below
repository
I think Marc told me to use that at one point.
Yup, that
Andrew Dunstan wrote:
In postgres.cvsup:
# complete distribution, including all below
pgsql
earthdistance
I've been using this in postgres.cvsup
# complete distribution, including all below
repository
I think Marc told me to use that at one point.
Joe
---(end of broadcas
I wrote:
I've been trying to set up a cvsup mirror following the instructions
at http://developer.postgresql.org/docs/postgres/cvsup.html
However, it seems to be awry w.r.t. the earthdistance module. Could
some kind person please tell me what needs to be done in either the
cvsup config or the m
Tom Lane <[EMAIL PROTECTED]> writes:
> Daniel Ahlin <[EMAIL PROTECTED]> writes:
> > This is a two part patch against 7.4.5 implementing the option of
> > configuring what is now set using the #defined constant PG_KRB_SRVNAM
> > (the name of the service part of the kerberos principal the server
> >
I've been trying to set up a cvsup mirror following the instructions at
http://developer.postgresql.org/docs/postgres/cvsup.html
However, it seems to be awry w.r.t. the earthdistance module. Could some
kind person please tell me what needs to be done in either the cvsup
config or the modules fi
Daniel Ahlin <[EMAIL PROTECTED]> writes:
> This is a two part patch against 7.4.5 implementing the option of
> configuring what is now set using the #defined constant PG_KRB_SRVNAM
> (the name of the service part of the kerberos principal the server
> uses).
Is this a good idea? Offhand it just s
Fixed
On Sat, 25 Sep 2004, Andrew Dunstan wrote:
I am getting this. Looks like it started happening sometime yesterday.
[EMAIL PROTECTED] pgtmp]$ cvs -d
:pserver:[EMAIL PROTECTED]:2401/projects/cvsroot export -r HEAD
pgsql cvs export: Updating pgsql
U pgsql/COPYRIGHT
U pgsql/GNUmakefile.in
U
On Sun, 19 Sep 2004, Greg Stark wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
>
> > Greg Stark <[EMAIL PROTECTED]> writes:
> > > Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > >> 2) switching the locale at run time is too expensive when using the system
> > >> library.
> >
> > > Fwiw I did some
Hi
This is a two part patch against 7.4.5 implementing the option of
configuring what is now set using the #defined constant PG_KRB_SRVNAM
(the name of the service part of the kerberos principal the server
uses).
On the backend it can be configured by the (new) string option
krb_srvnam in postgre
I am getting this. Looks like it started happening sometime yesterday.
[EMAIL PROTECTED] pgtmp]$ cvs -d
:pserver:[EMAIL PROTECTED]:2401/projects/cvsroot export -r
HEAD pgsql
cvs export: Updating pgsql
U pgsql/COPYRIGHT
U pgsql/GNUmakefile.in
U pgsql/Makefile
U pgsql/README
U pgsql/README.CVS
Hi
This is a patch against 7.4.5 to make configure use the krb5-config in
the heimdal Kerberos 5 implementation to get compile flags (instead of
using preset values).
--- postgresql-7.4.5/configure.in 2004-08-18 05:11:25.0 +0200
+++ postgresql-7.4.5-mod/configure.in 2004-09-24 09:37:35.00
If the client is first to send during the SSL startup protocol, then
there's no problem: there can only be one byte waiting for us.
So it looks good from the SSL perspective.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscr
and whats the final result?, does this method is suitable ?
Is it possible for postgresql leaders to add this function in postgresql source code?
glibc does not support jalali and herbew and ... calendars, so postgresql does not support them too. we are planning to write some simple functions
>Jim C. Nasby
> On Wed, Sep 15, 2004 at 10:56:28PM +0100, Simon Riggs wrote:
> > There are many good ideas out there, yet it is almost impossible to find
> > somebody else to implement yours!
> >
> > The acid test is to try and write it...
> >
> > Overall, I agree VACUUM could do with some tuning -
29 matches
Mail list logo
