Re: [HACKERS] CLUSTER and synchronized scans and pg_dump et al

2008/1/28, Tom Lane <[EMAIL PROTECTED]>: > > Do we have nominations for a name? The first idea that comes to mind > is "synchronized_scanning" (defaulting to ON). "synchronized_sequential_scans" is a bit long, but contains the keyword "sequential scans", which will ring a bell with many, more so

Re: [HACKERS] configurability of OOM killer

2008/2/8, Tom Lane <[EMAIL PROTECTED]>: > > Martijn van Oosterhout <[EMAIL PROTECTED]> writes: > > On Thu, Feb 07, 2008 at 08:22:42PM +0100, Dawid Kuroczko wrote: > >> while we are at it -- one feature would be great for 8.4, an > >> ability to shange shared buffers size "on the fly". > > > Sha

Re: [HACKERS] PostgreSQL 8.4 development plan

2008/2/8, Heikki Linnakangas <[EMAIL PROTECTED]>: > Gregory Stark wrote: > > git or its ilk would impact the lives of submitters and reviewers most. > > Basically it would allow two non-committers to collaborate, something which we > > can't really do effectively now. > > Two git-using non-committe

Re: [HACKERS] Batch update of indexes on data loading

when the new index is ready, in order to delete the old index, elevate that lock to an exclusive one? Markus -- Markus Bertheau Blog: http://www.bluetwanger.de/blog/ ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an ap

Re: [HACKERS] [PHP] WebDB Developers Wanted

On Mon, 2002-09-16 at 10:52, Christopher Kings-Lynne wrote: > Developers mailing list: [EMAIL PROTECTED] Hmm, that list does not appear on the sourceforge Lists page. Why? -- Markus Bertheau. Berlin, Berlin. Germany. ---(end of broadc

Re: [HACKERS] UTF8 and KOI8 mini-howto

В Птн, 13.06.2003, в 20:02, Oleg Bartunov пишет: > Hi there, > > I've managed to get postgresql working with UTF8 and KOI8. > Here is some mini-howto: > http://www.sai.msu.su/~megera/postgres/utf8.html The correct name for UTF-8 locales is xx_XX.UTF-8, not upper case and th

Re: [HACKERS] UTF8 and KOI8 mini-howto

В Вск, 15.06.2003, в 21:08, Markus Bertheau пишет: > The correct name for UTF-8 locales is xx_XX.UTF-8, not upper case and s/not/note/ > the minus. -- Markus Bertheau. Berlin, Berlin. Germany. ---(end of bro

Re: [HACKERS] UTF8 and KOI8 mini-howto

his setup here, any idea why this is the case? -- Markus Bertheau. Berlin, Berlin. Germany. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

Re: [GENERAL] [HACKERS] UTF8 and KOI8 mini-howto

В Пнд, 16.06.2003, в 01:26, Oleg Bartunov пишет: > Markus, > > I suspect lower,upper will not works with Unicode. It doesn't work with KOI8-R here, too. -- Markus Bertheau. Berlin, Berlin. Germany. ---(end of broadcast)--- TIP 2: y

[HACKERS] cvs build failure

Hi, I'm trying to build cvs, but it fails: bison -y -d preproc.y preproc.y:6214: fatal error: maximum table size (32767) exceeded make[4]: *** [preproc.h] Error 1 make[4]: Leaving directory `/home/bert/src/pgsql/src/interfaces/ecpg/preproc' What's the problem? -- Markus B

Re: [HACKERS] cvs build failure

В Втр, 01.07.2003, в 21:41, Larry Rosenman пишет: > what version of bison are you using? I believe we require 1.875 these days. 1.35. I'll upgrade. Thanks. -- Markus Bertheau. Berlin, Berlin. Germany. ---(end of broadcast)--- TIP 8:

[HACKERS] make check fails: user "postgres" doesn't exist

createdb failed make: *** [check] Ошибка 2 -- Markus Bertheau. Berlin, Berlin. Germany. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings

Re: [HACKERS] make check fails: user "postgres" doesn't exist

В Втр, 01.07.2003, в 22:53, Jeff пишет: > On Tue, Jul 01, 2003 at 10:28:12PM +0200, Markus Bertheau wrote: > > make check fails, and I have absolutely no idea where to look: > > > > running on port 65432 with pid 631 > > == cr

Re: [HACKERS] make check fails: user "postgres" doesn't exist

В Втр, 01.07.2003, в 23:30, Tom Lane пишет: > Markus Bertheau <[EMAIL PROTECTED]> writes: > > make check fails, and I have absolutely no idea where to look: > > > running on port 65432 with pid 631 > > == creating database "regression"

Re: [HACKERS] cvs build failure

see overriding as an advantage, too, because misparsing of the bison version string would just be a bug that had to be fixed, imo. You can as well modify configure in that case to make it compile, and send the patch to the bison version parser in afterwards. Maybe add a comment to the Makefile

Re: [HACKERS] cvs build failure

В Срд, 02.07.2003, в 01:10, Alvaro Herrera пишет: > On Wed, Jul 02, 2003 at 12:56:11AM +0200, Markus Bertheau wrote: > > > Maybe add a comment to the Makefile where bison is called that gives a > > hint to the user in case bison fails. > > Not too many people read Makefi

Re: [HACKERS] Building beta packaging fails ...

В Втр, 05.08.2003, в 05:23, The Hermit Hacker пишет: > /usr/bin/cvs -d /cvsroot -q checkout -rREL7_4_BETA1 -P pgsql > /usr/bin/find pgsql -type d -name CVS -print | xargs rm -rf Hint: cvs export -- Markus Bertheau <[EMAIL PROTECTED]> signature.asc Description: =?koi8-r?Q?=FC=D4=C

Re: [HACKERS] GUC variable for setting number of local buffers

with temp tables in a given session. So I was thinking about > making the default value fairly robust, maybe 1000 (as compared to > the historical value of 64...). Why does the dba need to set that variable at all then? -- Markus Bertheau <[EMAIL PROTECTED]> signature.asc Descr

Re: [HACKERS] CVS HEAD problem: psql: symbol lookup error:

ing through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so that your > message can get through to the mailing list cleanly -- Markus Bertheau <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part

Re: [HACKERS] patches for items from TODO list

ncode the XML output as UTF-8, which would make the files more readable for humans if the text data is not ASCII. Markus -- Markus Bertheau <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part

Re: [HACKERS] [SQL] ARRAY() returning NULL instead of ARRAY[] resp. {}

Dnia 24-05-2005, wto o godzinie 00:06 -0400, Tom Lane napisał(a): > Joe Conway <[EMAIL PROTECTED]> writes: > > Markus Bertheau wrote: > >> why does SELECT ARRAY(SELECT 1 WHERE FALSE) return NULL instead of > >> ARRAY[] resp. '{}'? > > > W

Re: [HACKERS] pg_autovacuum next steps

Ð ÐÐÐ, 22.03.2004, Ð 00:12, Tom Lane ÐÐÑÐÑ: > Please repost in some less proprietary format. Plain text is generally > considered the thing to use on this list. -- Markus Bertheau <[EMAIL PROTECTED]> pg_autovacuum Version 2 Design Document: Exec Summary: pg_autovacuum was initia

Re: [HACKERS] [GENERAL] unicode error and problem

NICODE to UTF-8 because UNICODE really just isn't an encoding. -- Markus Bertheau <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 8: explain analyze is your friend

Re: [HACKERS] Rough draft for Unicode-aware

1 make[1]: Leaving directory `/home/bert/src/postgresql-7.4.2/doc' make: *** [install] Error 2 [EMAIL PROTECTED] postgresql-7.4.2]$ make and make check worked ok. -- Markus Bertheau <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] Big problem

tmaster, have a beer. The question whether we should prevent this from happening stands; I think we should. -- Markus Bertheau <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

Re: [HACKERS] [pgsql-advocacy] Not 7.5, but 8.0 ?

ause after that, we don't have any more major number to jump into > without going into 2 digits. What's the problem with 7.10? -- Markus Bertheau <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

[HACKERS] [Fwd: Re: [SQL] multi column foreign key for implicitly unique columns]

Hi hackers, can this be made a TODO? Thanks -- Markus Bertheau <[EMAIL PROTECTED]> --- Begin Message --- Markus Bertheau wrote: Hi, PostgreSQL doesn't allow the creation of a foreign key to a combination of fields that has got no dedicated unique key but is unique nonetheless becau

[HACKERS] [Fwd: [BUGS] pg_autovacuum segv]

Forwarding to -hackers as per README -Пересланное сообщение- From: Markus Bertheau <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: [BUGS] pg_autovacuum segv Date: 09 Oct 2003 17:30:48 +0200 (gdb) run Starting program: /root/src/postgresql-7.4beta4/contrib/pg_autovacuum/pg_auto

[HACKERS] TODO item psql schema completion already implemented

schema_a.tab completes the table. -- Markus Bertheau <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 8: explain analyze is your friend

Re: [HACKERS] \xDD patch for 7.5devel

ed numeric equivalents into this > macro? What not ASCII compatible character sets are out there in use still today? -- Markus Bertheau <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

[HACKERS] Status of TODO item remove postmaster -o options

ead), with the intention of removing it in > 7.3. I didn't find such a notice in the 7.2 release notes. Markus Bertheau ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq

[HACKERS] Status of TODO: postgresql.conf: reset to default when commented

Hi, What's the status of the TODO item "Allow commenting of variables in postgresql.conf to restore them to defaults Currently, if a variable is commented out, it keeps the previous uncommented value until a server restarted." I take that to apply to the configuration re-read at

[HACKERS] pg.conf re-reading in signal handler or at next return to main loop?

er() calls ProcessConfigFile() which calls ParseConfigFile() which reads postgresql.conf. For me that means that postgresql.conf in read in the signal handler, which contradicts the claim in the README. Where's my error? Markus Bertheau ---(end of broadcast)--

Re: [HACKERS] pg.conf re-reading in signal handler or at next return to main loop?

2006/3/6, Tom Lane <[EMAIL PROTECTED]>: > > The comment is referring to the control flow in a backend; you're > looking at the postmaster's sighup handler, which is different. Then the following comment patch is appropriate, afaics. Markus Bertheau Index

[HACKERS] Plan for resetting commented postgresql.conf vars at sighup

Hi, this is the plan: In ParseConfigFile, record the fact that the variable was set in response to SIG_HUP in the status field (GUC_SET_FROM_SIGHUP). After setting all variables in postgresql.conf, set all variables that can appear in postgresql.conf (GUC_DISALLOW_IN_FILE), don't have their built-

[HACKERS] psql -p 5433; create database test; \c test failing

connections on Unix domain socket "/tmp/.s.PGSQL.5432"? Previous connection kept Why is it trying to use 5432? Am I missing something? Is that the expected behaviour? Michael Fuhr hinted that http://archives.postgresql.org/pgsql-committers/2006-02/msg00139.php may be the cause of that. Marku

Re: [HACKERS] Seperate command-line histories for seperate databases

e name does not unambiguously identify a database, but having a history for each database name is already an improvement over the current situation. Markus Bertheau ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

Re: [HACKERS] array_to_column function

" for every database. -- Markus Bertheau <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

Re: [HACKERS] [PATCHES] CVS should die

what the subversion book has to say about that: http://svnbook.red-bean.com/svnbook-1.1/ch05.html#svn-ch-5-sect-1.2.A We use svn over ssh and recently switched to fsfs because of the umask problem and because read-only access to bdb causes writes to the database. -- Markus Berthea

Re: [HACKERS] Update TIP 9 please

the planner will ignore your desire to choose an index scan if > your joining column's datatypes do not match (upgrade to 8.0!) > > We could change this now... > > ...and add another TIP to encourage people to upgrade...? > -- Markus Bertheau <[EMAIL PRO

Re: [HACKERS] prev main developer page

s? http://www.gnome.org/~jdub/blog/2005/Feb/11 > > thanks, > Jaime Casanova > > ---(end of broadcast)--- > TIP 4: Don't 'kill -9' the postmaster -- Markus Bertheau <[EMAIL PROTECTED]> signature.asc Des

Re: [HACKERS] [SQL] ARRAY() returning NULL instead of ARRAY[] resp. {}

В Втр, 24/05/2005 в 00:06 -0400, Tom Lane пишет: > Joe Conway <[EMAIL PROTECTED]> writes: > > Markus Bertheau wrote: > >> why does SELECT ARRAY(SELECT 1 WHERE FALSE) return NULL instead of > >> ARRAY[] resp. '{}'? > > > Why would you expect an

Re: [HACKERS] [SQL] ARRAY() returning NULL instead of ARRAY[] resp. {}

В Пнд, 06/06/2005 в 10:44 -0400, Tom Lane пишет: > Markus Bertheau =?UTF-8?Q?=E2=98=AD?= <[EMAIL PROTECTED]> writes: > > By analogy, array_upper('{}'::TEXT[], 1) should return 0 instead of > > NULL. > > No, that doesn't follow ... we've traditionally

Re: [HACKERS] [SQL] ARRAY() returning NULL instead of ARRAY[]

an 0. I don't know why it was decided to do that in the first place. It seems a rather odd feature to me. Markus -- Markus Bertheau ☭ <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send a

[HACKERS] quote_boolean() and friends missing

olean (), quote_date() and so on. For the sake of completeness I think these functions should exist. While the use of to_char() resp. decode() for some types is possible, it does feel like a workaround to me. Opinions? Do these functions belong in the PostgreSQL core? -- Markus Bertheau ☭ <[EMAIL P

Re: [HACKERS] quote_boolean() and friends missing

В Пнд, 20/06/2005 в 10:01 -0400, Tom Lane пишет: > Markus Bertheau =?UTF-8?Q?=E2=98=AD?= <[EMAIL PROTECTED]> writes: > > I'm writing an application with a lot of PL/pgSQL and am constructing > > SQL queries on the fly. The quote_literal() and quote_ident() functions &

Re: [HACKERS] quote_boolean() and friends missing

В Пнд, 20/06/2005 в 10:10 -0400, Tom Lane пишет: > Markus Bertheau =?UTF-8?Q?=E2=98=AD?= <[EMAIL PROTECTED]> writes: > > Maybe quote_* is not the right name, but the functionality is needed. > > I don't think so --- at least not in plpgsql, which can do this already. &g