Re: Improved ICU patch - WAS: [HACKERS] Implementing full UTF-8 support (aka supporting 0x00)

> 11 aug. 2016 kl. 11:15 skrev Palle Girgensohn : > >> >> 11 aug. 2016 kl. 03:05 skrev Peter Geoghegan : >> >> On Wed, Aug 10, 2016 at 1:42 PM, Palle Girgensohn >> wrote: >>> They've been used for the FreeBSD ports since 2005, and have

Re: Improved ICU patch - WAS: [HACKERS] Implementing full UTF-8 support (aka supporting 0x00)

> 11 aug. 2016 kl. 03:05 skrev Peter Geoghegan : > > On Wed, Aug 10, 2016 at 1:42 PM, Palle Girgensohn wrote: >> They've been used for the FreeBSD ports since 2005, and have served us well. >> I have of course updated them regularly. In this latest version, I'v

Improved ICU patch - WAS: [HACKERS] Implementing full UTF-8 support (aka supporting 0x00)

> 4 aug. 2016 kl. 02:40 skrev Bruce Momjian : > > On Thu, Aug 4, 2016 at 08:22:25AM +0800, Craig Ringer wrote: >> Yep, it does. But we've made little to no progress on integration of ICU >> support and AFAIK nobody's working on it right now. > > Uh, this email from July says Peter Eisentraut wi

[HACKERS] pg_upgrade fails in 9.6 beta1

Hi, When trying an upgrade from postgresql94 -> postgresql96 (beta1) using pg_upgrade: pg_upgrade -p 5433 -P 5434 -b /usr/local/bin -B /home/girgen/postgres96/bin -d /tank/opt96/pgsql/data94 -D /tank/opt96/pgsql/data96 -U pgsql96 -k I eventually get this: pg_restore: creating TABLE "public.

Re: [HACKERS] [pgsql-packagers] Palle Girgensohn's ICU patch

> 27 nov 2014 kl. 10:15 skrev Dave Page : > > > > On Thu, Nov 27, 2014 at 9:09 AM, Jakob Egger wrote: > Am 26.11.2014 um 17:46 schrieb Geoff Montee : > > This topic reminds me of a thread from a couple months ago: > > > > http://www.postgresql.org/message-id/f8268db6-b50f-429f-8289-da8ffa5f2..

Re: [HACKERS] [pgsql-packagers] Palle Girgensohn's ICU patch

> 27 nov 2014 kl. 16:03 skrev Tom Lane : > > Another issue is that (AFAIK) ICU doesn't support any non-Unicode > encodings, which means that a build supporting *only* ICU collations is a > nonstarter IMO. The patch I originally wrote replaces strwcoll but for keeps the original behaviour for 8-

Re: [HACKERS] [pgsql-packagers] Palle Girgensohn's ICU patch

> 26 nov 2014 kl. 20:42 skrev Peter Eisentraut : > > (A build > option and a more explicit warning might be nice.) In the freebsd ports, it is an option, default is off. :-) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www

Re: [HACKERS] [pgsql-packagers] Palle Girgensohn's ICU patch

> 26 nov 2014 kl. 14:06 skrev Palle Girgensohn : > > Well, this discussion actually pushes the priority quite a bit for me -- > someone else actually beeing interested about the patch... I thought it was > just me... :)= By "pushes the priority", I mean it gets more

Re: [HACKERS] [pgsql-packagers] Palle Girgensohn's ICU patch

> 26 nov 2014 kl. 15:56 skrev Neil Tiffin : > > > On Nov 26, 2014, at 8:21 AM, Greg Stark wrote: > >> I find it hard to believe the original premise of this thread. We knew >> there were some problems with OSX and FreeBSD but surely they can't be >> completely broken? > > Ever tried to use Sp

Re: [HACKERS] [pgsql-packagers] Palle Girgensohn's ICU patch

> 26 nov 2014 kl. 15:21 skrev Greg Stark : > > I find it hard to believe the original premise of this thread. We knew > there were some problems with OSX and FreeBSD but surely they can't be > completely broken? What happens if you run "ls" with your locale set > to something like fr_FR.UTF8 ? Do

Re: [HACKERS] [pgsql-packagers] Palle Girgensohn's ICU patch

> 26 nov 2014 kl. 11:44 skrev Jakob Egger : > > >> Am 26.11.2014 um 11:20 schrieb Dave Page : >> >> On Wed, Nov 26, 2014 at 10:13 AM, Jakob Egger wrote: >>> Am 26.11.2014 um 11:05 schrieb Dave Page : >>> >>> You may want to bear in mind that postgres.app is on the main PG >>> downloads page o

Re: [HACKERS] [pgsql-packagers] Palle Girgensohn's ICU patch

> 26 nov 2014 kl. 10:48 skrev Jakob Egger : > > >> Bear in mind that this might alter the way indexes are built. From the top >> of my head, I just can't remember if this is true or not. I'm probably >> wrong? Magnus? You would have to try. > > That's why I want to include it in the first ver

Re: [HACKERS] [pgsql-packagers] Palle Girgensohn's ICU patch

> 26 nov 2014 kl. 10:36 skrev Jakob Egger : > >> One of the >> big arguments against bringing it in then (because it worked) was that >> we'd bring in another compile time dependency that's actually larger >> than PostgreSQL itself. > > Magnus: I don't see how this is a problem as long as using

Re: [HACKERS] [pgsql-packagers] Palle Girgensohn's ICU patch

> 26 nov 2014 kl. 09:58 skrev Magnus Hagander : > > On Wed, Nov 26, 2014 at 8:41 AM, Palle Girgensohn wrote: >> Hi! >> >> This is indeed a very well tested patch as we've run it in production for 8+ >> years on 20+ systems. >> >> It is not inc

Re: [HACKERS] [pgsql-packagers] Palle Girgensohn's ICU patch

. As a consequence, text sorting > in PostgreSQL doesn't work. The only workaround seemed to be to use a legacy > encoding like latin1, which is inacceptable. > > I discovered that OS X shares this limitation with FreeBSD, and there exists > a patch written by Palle Girgensoh

Re: [HACKERS] Perfomance degradation 9.3 (vs 9.2) for FreeBSD

Hello, How did this testing turn out? Palle 3 jul 2014 kl. 12:15 skrev Tatsuo Ishii : > Hi, > >> Hi, >> >> Attached you can find a short (compile tested only ) patch implementing >> a 'shared_memory_type' GUC, akin to 'dynamic_shared_memory_type'. Will >> only apply to 9.4, not 9.3, but it sh

Re: [HACKERS] Keepalive-related socket options under FreeBSD 9, 10

> Since upgrading FreeBSD from 8 to 9, I've noticed the following messages > showing up in logs when a connection with pgAdmin3 is made: > > LOG: getsockopt(TCP_KEEPCNT) failed: Protocol not available > STATEMENT: SELECT setting FROM pg_settings WHERE name IN ('autovacuum', > 'track_counts') > L

Re: [HACKERS] Perfomance degradation 9.3 (vs 9.2) for FreeBSD

22 apr 2014 kl. 17:26 skrev Andrew Dunstan : > > On 04/22/2014 01:36 AM, Joshua D. Drake wrote: >> >> On 04/21/2014 06:19 PM, Andrew Dunstan wrote: >> >>> >>> If we never start we'll never get there. >>> >>> I can think of several organizations that might be approached to donate >>> hardware

Re: [HACKERS] Perfomance degradation 9.3 (vs 9.2) for FreeBSD

> 21 apr 2014 kl. 11:26 skrev Francois Tigeot : > >> On Sun, Apr 20, 2014 at 04:07:25PM +0200, Palle Girgensohn wrote: >> >>>> If mmap needs to perform well in the kernel, I'd like to know of someone >>>> with FreeBSD kernel knowledge who is in

Re: [HACKERS] Perfomance degradation 9.3 (vs 9.2) for FreeBSD

> 20 apr 2014 kl. 12:19 skrev Francois Tigeot : > > Hi, > >> On Sun, Apr 20, 2014 at 11:24:38AM +0200, Palle Girgensohn wrote: >> >> I see performance degradation with PostgreSQL 9.3 vs 9.2 on FreeBSD, and I'm >> wondering who to poke to mitigate

[HACKERS] leaking lots of unreferenced inodes (pg_xlog files?), maybe after moving tables and indexes to tablespace on different volume

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Running postgresql-9.2.2 on FreeBSD 9.1 using vanilla ufs file system. I have the postgresql base/ on the /usr disk, and a separate volume /opt where the default tablespace resides. I found many databases that had not used the default tablespace,

[HACKERS] Why does delete from table where not exists (select 1 from ... LIMIT 1) perform badly?

Hi, I've read about the reason for this before, but cannot find a reference to it now. How come the planner treats the delete from table where not extists(select 1 from table2 where ... LIMIT 1) so differently, and usually badly, when the LIMIT 1 is there. In older version of postgresql, I remem

Re: [HACKERS] alter table tablename add column - breaks pl/pgsql function returns tablename

5 nov 2012 kl. 22:23 skrev Tom Lane : > Palle Girgensohn writes: >> Please note that this problem does not go away by disconnecting and >> reconnecting, and other sessions get the error immediately, so the claim >> that it is bound to a session is false. > > Huh?

Re: [HACKERS] alter table tablename add column - breaks pl/pgsql function returns tablename

5 nov 2012 kl. 19:36 skrev Robert Haas : > On Thu, Nov 1, 2012 at 12:14 AM, Amit kapila wrote: >>> Is this very hard to fix? >> >> Currently the compiled body is not discarded on DDL's, so I believe it is >> not a bug as per current implementation. >> However it can be thought of as a new

[HACKERS] alter table tablename add column - breaks pl/pgsql function returns tablename

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! This is an old problem, referred to in bug #4907: CREATE TABLE test(id INTEGER); INSERT INTO test VALUES (1); CREATE OR REPLACE FUNCTION test_func() returns SETOF test as $$ DECLARE res_ test; BEGIN FOR res_ IN SELECT * FROM test LOOP

[HACKERS] build postgresql on Mac OS X mountain lion with ossp-uuid

Hi, On the new Darwin 10.8 (aka mountain lion), I had to add #ifdef __APPLE__ #if (__ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__ >= 1080) #define _XOPEN_SOURCE #endif #endif to the very beginning of contrib/uuid-ossp/uuid-ossp.c to get the build working with --with-ossp-uuid. I suggested someth

Re: [HACKERS] [ANNOUNCE] PostgreSQL Core Team

Grattis Magnus! ;-) --On 27 april 2011 19.48.48 +0100 Dave Page wrote: I'm pleased to announce that effective immediately, Magnus Hagander will be joining the PostgreSQL Core Team. Magnus has been a contributor to PostgreSQL for over 12 years, and played a major part in the development and on

[HACKERS] no duration logging when using JDBC?

Hi! When using JDBC (8.0.311) to connect to a 8.0.3 database, with log_duration = true nothing happens. For psql connections, it works fine, but not for JDBC connections. Surely a bug? Is it fixed in the 8.1 branch? Also, as I mailed about a while back, when using prepared statements, the p

Re: [HACKERS] Win32 unicode vs ICU

--On måndag, augusti 22, 2005 10.12.11 -0400 Tom Lane <[EMAIL PROTECTED]> wrote: Palle Girgensohn <[EMAIL PROTECTED]> writes: wrote: How is FreeBSD's Unicode support broken? I was not aware of that. FreeBSD has no unicode collation support. Hence the need for

Re: [HACKERS] Win32 unicode vs ICU

--On måndag, augusti 22, 2005 09.19.58 -0400 Bruce Momjian wrote: Palle Girgensohn wrote: > I feel it makes sense to apply the smaller patch in any case, so that > there's a Win32 solution not requiring ICU (ie, I can't see an argument > for doing (2) rather than (3)). >

Re: [HACKERS] Win32 unicode vs ICU

--On lördag, augusti 20, 2005 12.17.47 -0400 Tom Lane <[EMAIL PROTECTED]> wrote: [ moving to -hackers for wider discussion ] "Magnus Hagander" <[EMAIL PROTECTED]> wrote in http://archives.postgresql.org/pgsql-patches/2005-08/msg00039.php I've been working with Palles ICU patch to make it wor

[HACKERS] problem building 7.3 on FreeBSD 6

Hi! Can someone with a FreeBSD 6.x installation confirm the build error referred here: I maintain the postgresql ports for FreeBSD, but I have no version 6 installed yet. Thanks, Palle ---

Re: [HACKERS] More buildfarm stuff

--On tisdag, juli 26, 2005 15.17.57 -0400 Tom Lane <[EMAIL PROTECTED]> wrote: Larry Rosenman writes: On Jul 26 2005, Jim C. Nasby wrote: So the question now is: how do we fix the issue with threaded python? how do we get libc_r into the mix on FreeBSD 4.11? A possible compromise is to a

Re: [HACKERS] More buildfarm stuff

--On tisdag, juli 19, 2005 15.11.31 -0400 Tom Lane <[EMAIL PROTECTED]> wrote: "Jim C. Nasby" <[EMAIL PROTECTED]> writes: http://archives.postgresql.org/pgsql-bugs/2005-07/msg00096.php describes what I think is causing octopus to fail. What's also interesting is these patches from the FreeBSD

[HACKERS] --enable-thread-safety?

Hi! Need a piece of advice here. I'm wrapping up the ports for FreeBSD, and jus wonder if it is perhaps clever to always add --enable-thread-safety to the configure args. Is there a big enough penalty for having it off by default, or can I just have it on always? /Palle

Re: [HACKERS] Patch for collation using ICU

> Palle Girgensohn <[EMAIL PROTECTED]> writes: >>> I'm confused. I thought the ICU patches is intended for using on >>> broken locale platforms? > >> It will sort correctly in *one* locale, using ICU. You still cannot mix >> different locales in the

Re: [HACKERS] Patch for collation using ICU

--On söndag, maj 08, 2005 22.19.25 +0900 Tatsuo Ishii <[EMAIL PROTECTED]> wrote: > > > On Sun, May 08, 2005 at 02:07:29PM +1000, John Hansen wrote: > > > > Tatsuo Ishii wrote: > > > > > > > > So Japanese(including ASCII)/UNICODE behavior is > > > perfectly correct > > > > > at this moment. > > >

Re: [HACKERS] Patch for collation using ICU

--On lördag, maj 07, 2005 10.58.09 -0400 Tom Lane <[EMAIL PROTECTED]> wrote: "John Hansen" <[EMAIL PROTECTED]> writes: Where'd you get the licence from? It was the first thing I came across in their docs: http://icu.sourceforge.net/userguide/intro.html Looking more closely, it may be that this lice

Re: [HACKERS] Patch for collation using ICU

--On lördag, maj 07, 2005 10.06.43 -0400 Bruce Momjian wrote: Palle Girgensohn wrote: --On l?rdag, maj 07, 2005 23.15.29 +1000 John Hansen <[EMAIL PROTECTED]> wrote: > Btw, I had been planning to propose replacing every single one of the > built in charset conversion functions w

Re: [HACKERS] Patch for collation using ICU

--On lördag, maj 07, 2005 09.52.59 -0400 Bruce Momjian wrote: Palle Girgensohn wrote: >> Also, apparently, ICU is installed by default in many linux >> distributions, and usually it is version 2.8. Some linux users have >> asked me if there are plans for a patch that

Re: [HACKERS] Patch for collation using ICU

--On lördag, maj 07, 2005 23.33.31 +1000 John Hansen <[EMAIL PROTECTED]> wrote: -Original Message- From: Palle Girgensohn [mailto:[EMAIL PROTECTED] Sent: Saturday, May 07, 2005 11:33 PM To: John Hansen; Bruce Momjian Cc: pgsql-hackers@postgresql.org Subject: RE: [HACKERS] Pat

Re: [HACKERS] Patch for collation using ICU

nal Message- From: John Hansen Sent: Saturday, May 07, 2005 11:09 PM To: 'Palle Girgensohn'; 'Bruce Momjian' Cc: 'pgsql-hackers@postgresql.org' Subject: RE: [HACKERS] Patch for collation using ICU > --On lördag, maj 07, 2005 22.53.46 +1000 John Hansen >

Re: [HACKERS] Patch for collation using ICU

--On lördag, maj 07, 2005 22.22.52 +1000 John Hansen <[EMAIL PROTECTED]> wrote: I use this patch in production on one FreeBSD 4.10 server at the moment. With the latest version, I've had no problems. Logging is swithed on for now, and it shows no signs of ICU complaining. I'd like more reports o

Re: [HACKERS] Patch for collation using ICU

--On lördag, maj 07, 2005 23.25.15 +1000 John Hansen <[EMAIL PROTECTED]> wrote: Palle Girgensohn wrote: I'm aware of that. It might help for unicode, but there are a bunch of other encodings. IANA has decided that utf-8 has *no* aliases, hence only utf-8 (with dash, but case ins

Re: [HACKERS] Patch for collation using ICU

--On lördag, maj 07, 2005 08.37.05 -0400 Bruce Momjian wrote: Palle Girgensohn wrote: > > Is this patch ready for application? I don't think so, not quite. I have not had any positive reports from linux users, this is only tested in a FreeBSD environment. I'd say it needs so

Re: [HACKERS] Patch for collation using ICU

ssage- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Hansen Sent: Saturday, May 07, 2005 10:23 PM To: Palle Girgensohn; Bruce Momjian Cc: pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Patch for collation using ICU > > I use this patch in production on one FreeBS

Re: [HACKERS] Patch for collation using ICU

now, and it shows no signs of ICU complaining. I'd like more reports on Linux, though. /Palle - -- Palle Girgensohn wrote: Hi! I've put together a patch for using IBM's ICU package for collation. If your OS does not have full support for collat

Re: [HACKERS] Patch for collation using ICU

--On fredag, maj 06, 2005 23.31.20 -0400 Tom Lane <[EMAIL PROTECTED]> wrote: Bruce Momjian writes: Is this patch ready for application? Not until ICU is released under a BSD license ... It's not GPL anyway. Seems pretty much like the BSD license, at least more BSD-ish than GPL-ish.

Re: [HACKERS] prepared statements don't log arguments?

--On torsdag, april 07, 2005 23.31.52 +0100 Simon Riggs <[EMAIL PROTECTED]> wrote: On Wed, 2005-04-06 at 15:01 +0200, Palle Girgensohn wrote: I really need to know the *real* arguments... Why do you need to log the arguments as well? Debugging purposes. If I fealize there are queries hoggi

Re: [HACKERS] prepared statements don't log arguments?

--On torsdag, april 07, 2005 14.34.22 +1200 Oliver Jowett <[EMAIL PROTECTED]> wrote: Greg Stark wrote: Palle Girgensohn <[EMAIL PROTECTED]> writes: When setting log_statement = all, and using JDBC PreparedStatements, I get $n in the log where the real arguments used to be in previous

[HACKERS] prepared statements don't log arguments?

Hi! When setting log_statement = all, and using JDBC PreparedStatements, I get $n in the log where the real arguments used to be in previous versions of postgresql: postgres[30059]: [97-1] LOG: statement: INSERT INTO group_data (this_group_id, item_text, link_path) VALUES ($1, $2, $3) I reall

Re: [HACKERS] Patch for collation using ICU

--On söndag, mars 27, 2005 04.34.03 +0300 Hannu Krosing <[EMAIL PROTECTED]> wrote: On L, 2005-03-26 at 03:09 +0100, Palle Girgensohn wrote: Hi! ... I've noticed a couple of things about using the ICU patch vs. pristine pg-8.0.1: - ORDER BY is case insensitive when using ICU. This migh

Re: [HACKERS] Patch for collation using ICU

--On söndag, mars 27, 2005 20.11.48 +0200 Magnus Hagander <[EMAIL PROTECTED]> wrote: As for general collation of unicode, the reason for me to use ICU is that my system does not support strcoll correctly for multibyte locales, as I mentioned earlier. I also noted that even for systems that do ha

Re: [HACKERS] Patch for collation using ICU

--On lördag, mars 26, 2005 17.40.01 -0800 Stephan Szabo <[EMAIL PROTECTED]> wrote: On Sun, 27 Mar 2005, Palle Girgensohn wrote: --On lördag, mars 26, 2005 08.16.01 -0800 Stephan Szabo <[EMAIL PROTECTED]> wrote: > On Sat, 26 Mar 2005, Palle Girgensohn wrote: >> I've

Re: [HACKERS] Patch for collation using ICU

--On lördag, mars 26, 2005 13.59.19 +1100 John Hansen <[EMAIL PROTECTED]> wrote: - ORDER BY is case insensitive when using ICU. This might break the SQL standard (?), but sure is nice :) This would mean that indexes are also case insensitive right? Which makes it a Bad Thing(tm). Well, no, not r

Re: [HACKERS] Patch for collation using ICU

--On lördag, mars 26, 2005 08.16.01 -0800 Stephan Szabo <[EMAIL PROTECTED]> wrote: On Sat, 26 Mar 2005, Palle Girgensohn wrote: I've noticed a couple of things about using the ICU patch vs. pristine pg-8.0.1: - ORDER BY is case insensitive when using ICU. This might break the S

Re: [HACKERS] Patch for collation using ICU

--On lördag, mars 26, 2005 10.42.19 +1100 John Hansen <[EMAIL PROTECTED]> wrote: FYI, I also found that initdb crashes with error 139 on any locale other than C/POSIX. Odd, not for me, but I did make a bad assumption about character encoding. Perhaps the new patch will help? (see previous mail)

Re: [HACKERS] Patch for collation using ICU

--On fredag, mars 25, 2005 00.40.04 +0100 Palle Girgensohn <[EMAIL PROTECTED]> wrote: Hi! I've put together a patch for using IBM's ICU package for collation. If your OS does not have full support for collation ur uppercase/lowercase in multibyte locales, this might be useful. If

Re: [HACKERS] Patch for collation using ICU

--On fredag, mars 25, 2005 09.53.38 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: Palle Girgensohn <[EMAIL PROTECTED]> writes: hmm... I think I might have made a false assumption that the locale string would contain the character encoding. You certainly cannot assume that. Would tha

Re: [HACKERS] Patch for collation using ICU

/Palle ... John -Original Message- From: John Hansen Sent: Friday, March 25, 2005 10:27 PM To: 'Palle Girgensohn'; 'pgsql-hackers@postgresql.org' Subject: RE: [HACKERS] Patch for collation using ICU > --On fredag, mars 25, 2005 16.34.41 +1100 John Hansen > <[EMAI

Re: [HACKERS] Patch for collation using ICU

2 as port. I can check the older version, I doubt it would too much difference. Some autoconf sorcery needed, perhaps. /Palle ... John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Palle Girgensohn Sent: Friday, March 25, 2005 10:40 AM To: pgsql-hacker

[HACKERS] Patch for collation using ICU

Hi! I've put together a patch for using IBM's ICU package for collation. If your OS does not have full support for collation ur uppercase/lowercase in multibyte locales, this might be useful. If you are using a multibyte character encoding in your database and want collation, i.e. order by, and

[HACKERS] where is the locale set for each server instance?

Hi! I'm pluggin ICU into PostgreSQL for unicode collation, since FreeBSD has no support for unicode collation. It works fine, but I cannot find out where to set the default locale for each backend instance. I want to use the LC_COLLATE used in initdb, now I've just hard wired it for my own needs

Re: [HACKERS] Bug? 8.0 does not use partial index

--On fredag, januari 14, 2005 11.52.38 +1100 John Hansen <[EMAIL PROTECTED]> wrote: > Dunno if you're desperate enough to try that ... but it does seem to > work. if yo're going to hack anyway, then why not just simply tell the planner that you know better and that it should use the index, regard

Re: [HACKERS] Bug? 8.0 does not use partial index

--On torsdag, januari 13, 2005 19.32.38 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: I wrote: I thought of a fairly miserable hack, which relies on the fact that 8.0 does know how to accumulate statistics on functional indexes: Never mind, it turns out that doesn't work the way I thought. It's act

Re: [HACKERS] Bug? 8.0 does not use partial index

--On torsdag, januari 13, 2005 19.44.57 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: Palle Girgensohn <[EMAIL PROTECTED]> writes: Trying all this out, I realize that on 7.4.5, I can sometimes get different results after `vacuum analyze' vs. a plain `analyze' (again, not

Re: [HACKERS] Bug? 8.0 does not use partial index

--On torsdag, januari 13, 2005 18.55.11 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: Palle Girgensohn <[EMAIL PROTECTED]> writes: --On torsdag, januari 13, 2005 18.18.37 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: So there's something nuts about the statistics in this case. O

Re: [HACKERS] Bug? 8.0 does not use partial index

--On torsdag, januari 13, 2005 17.03.41 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: Palle Girgensohn <[EMAIL PROTECTED]> writes: How do you mean they look far off? Seq Scan on group_data (cost=0.00..47544.43 rows=114164 width=43) (actual time=114.015..1334.479 rows=4 loops=1) 1141

Re: [HACKERS] Bug? 8.0 does not use partial index

Thanks, but the behaviour seems identical. :( /Palle --On fredag, januari 14, 2005 07.37.46 +1100 John Hansen <[EMAIL PROTECTED]> wrote: create index foo on group_data(this_group_id) where group_id is null; Try this instead; create index foo on group_data(this_group_id) where nullvalue(group_id);

Re: [HACKERS] Bug? 8.0 does not use partial index

elect count(this_group_id) from group_data where this_group_id=46 and group_id is null; count --- 4 (1 row) Time: 1,635 ms /Palle --On torsdag, januari 13, 2005 16.33.58 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: Palle Girgensohn <[EMAIL PROTECTED]> writes: On 7.4.5, it uses

[HACKERS] Bug? 8.0 does not use partial index

Hi! Here's an odd thing. I use a partial index on a table: group_data CREATE TABLE group_data ( this_group_id integer NOT NULL, group_id integer -- ... ); create index foo on group_data(this_group_id) where group_id is null; there are approx 1 million tuples where this_group_id=46, but only 4

Re: [HACKERS] getting 'order by' working with unicode locale? ICU?

--On torsdag, december 16, 2004 09.20.50 +0100 Peter Eisentraut <[EMAIL PROTECTED]> wrote: Palle Girgensohn wrote: Not on FreeBSD, since collation is not implemented in unicode locales. One way would be to implement it in the OS, of course... Try taking the locale definition files from a

Re: [HACKERS] getting 'order by' working with unicode locale? ICU?

--On onsdag, december 15, 2004 23.21.13 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: Palle Girgensohn <[EMAIL PROTECTED]> writes: I'm using Postgresql on FreeBSD, and would like to get "order by" to work with unicode. What makes you think it doesn't? Use the rig

[HACKERS] getting 'order by' working with unicode locale? ICU?

Hi! I'm using Postgresql on FreeBSD, and would like to get "order by" to work with unicode. The OS does have collation implemented for unicode (UTF-8) locales. Some freebsd people point me towards IBM:s ICU kit. How much effort would be required to get postgresql to sort properly, mainly using

Re: [HACKERS] are there any cons to linking libstdc++ with

Does the same arguments apply for linking with libc_r (pthreads)? It is needed by plpython, at least on FreeBSD 4.10 (probably all versions). /Palle --On onsdag, november 17, 2004 20.49.20 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: Palle Girgensohn <[EMAIL PROTECTED]> writes: Is the

[HACKERS] are there any cons to linking libstdc++ with postgresql?

Hi! I'm not a linking guru... Is there a penalty for setting LDFLAGS+= -lstdc++ when building postgresql? Postgis includes a bunch of useful functions for manipulating spatial data. Some of them are provided by geos, a separate c++ library, with postgis providing wrappers. According to postgis do

Re: [HACKERS] [BUGS] PostgreSQL client has problems when libbind is

it working. ----- -- Palle Girgensohn wrote: Was this problem fixed? Can I request the problem report @ FreeBSD to be closed? Thanks, Palle --On torsdag, juni 12, 2003 18.51.18 -0400 "Yves R. Crevecoeur" <[EMAIL PROTECTED]> wrote: > Don't break BeOS suppo

Re: [HACKERS] [BUGS] PostgreSQL client has problems when libbind is installed

ww.yellowtab.com http://www.yellowtab.com/board/ http://www.yellowtab.com/support/ Regards, Yves - Original Message - From: "Tom Lane" <[EMAIL PROTECTED]> To: "Palle Girgensohn" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; "Tom Alsberg" <[EMAI

[HACKERS] why was libpq.so version bumped?

Hi! subject says it all, I guess. There is hardly no difference between 7.3 libpq and 7.3.1 libpq. Why the version shift? Isn't the only thing rectifying a version shift that there is a change in the API. Maybe there is, but I cannot find it. If there is a good reason, like say "security", may

Re: [HACKERS] why was libpq.so's version number bumped?

Still am. ;-) --On tisdag, december 31, 2002 10.01.34 +0800 Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote: On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote: > ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ?? I forgot one other possible answer: perhaps the port maintai

Re: [HACKERS] why was libpq.so's version number bumped?

--On måndag, december 30, 2002 06.35.22 -0500 Dan Langille <[EMAIL PROTECTED]> wrote: On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote: ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ?? I forgot one other possible answer: perhaps the port maintainer is taking a well deser

[HACKERS] why was libpq.so's version number bumped?

Hi! subject says it all, I guess. There is hardly no difference between 7.3 libpq and 7.3.1 libpq. Why the version shift? Isn't the only thing rectifying a version shift that there is a change in the API. Maybe there is a change, but I cannot find it. One of the reasons I ask is, if it is a go