PgSql

[HACKERS] Make archiver check for SIGHUP more often?
There's a complaint over here http://archives.postgresql.org/pgsql-general/2010-05/msg00365.php about the archiver process not being very swift to adopt a new value of archive_command. This is because it only reacts to SIGHUP once per outer loop, ie, only after completing an archiving cycle. This is unhelpful in ... 10 May 2010 22:07

9.0b1: "ERROR: btree index keys must be ordered byattribute"
On Sun, May 09, 2010 at 05:48:27PM +0900, Ian Barwick wrote: Hi I've just compiled the 9.0 beta1 source tarball and am testing my custom application against it (which has been running on PostgreSQL since 7.3 or so). The below statement results in the following error message: "ERROR: btr... 9 May 2010 11:03

plpython3
On Feb 1, 2010, at 12:18 PM, James William Pye wrote: Right now, I'm trying to trim some of the easy issues[1] and getting a project web page up. I expect to be able to make a release soon, and I'll follow-up to this thread when I do. Well, I ended up doing some others things at that point in time, but I have ma... 8 May 2010 16:43

[GENERAL] psql weird behaviour with charset encodings
> However, it appears that glibc's printf code interprets the parameter as the number of *characters* to print, and to determine what's a character it assumes the string is in the environment LC_CTYPE's encoding. Well, I myself have problems to believe that :-) This would be nasty... Are you sure? I couldn re... 8 May 2010 22:10

Two C-interface issues on -Testers
Josh Berkus <josh(a)agliodbs.com> writes: Can someone verify that these two C interface issues are intentional? If not, they're bugs: http://archives.postgresql.org/pgsql-testers/2010-05/msg00011.php http://archives.postgresql.org/pgsql-testers/2010-05/msg00010.php That's ecpg, not "C interface" --- the la... 7 May 2010 15:37

[HACKERS] Two C-interface issues on -Testers
All, BTW, it would be good if some other folks than me were monitoring -testers. Can someone verify that these two C interface issues are intentional? If not, they're bugs: http://archives.postgresql.org/pgsql-testers/2010-05/msg00011.php http://archives.postgresql.org/pgsql-testers/2010-05/msg00010.php -... 7 May 2010 14:31

beta to release
Robert Haas <robertmhaas(a)gmail.com> writes: I am fuzzier on what happens now. I understand that it depends on what bug reports we get as a result of beta testing, but what I don't quite know is what the expectations are for individual developers, how we're tracking what issues still need to be resolved, or... 8 May 2010 10:06

[HACKERS] beta to release
On Mon, Jan 11, 2010 at 10:45 PM, Bruce Momjian <bruce(a)momjian.us> wrote: What amazes me is how many people who closely follow our development are mystified by what we do during that pre-beta period. Hey, I'm still mystified.  Maybe you and Tom could do twice-a-week status updates on what you're... 7 May 2010 11:09

no universally correct setting for fsync
On Fri, May 7, 2010 at 9:47 AM, Kevin Grittner <Kevin.Grittner(a)wicourts.gov> wrote: Someone just posted to the -admin list with a database corrupted while running with fsync=off.  I was all set to refer him to the documentation explaining why he should stop doing this, but to my surprise the documentation ... 31 May 2010 11:58

[HACKERS] no universally correct setting for fsync
Someone just posted to the -admin list with a database corrupted while running with fsync=off. I was all set to refer him to the documentation explaining why he should stop doing this, but to my surprise the documentation waffles on the issue way past what I think is reasonable. http://www.postgresql.org/docs/... 7 May 2010 10:02