[HACKERS]

Hi,     I am now studying PostgreSQL.   in your web site: Developer's Frequently Asked Questions (FAQ) for PostgreSQL Technical Questions 2.1) How do I efficiently access information in tables from the backend code? Since heap_open function needs the oid of the relation, h

Re: [HACKERS] compiling source code!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Also, I would recommend uninstalling cygwin before you install mingw, because if the mingw doesn't behave properly (gcc won't compile files etc...), you could be sure that there definitely is a conflict between the cygwin and mingw. If you don't wish to uninstall cygwin, at least rename the

Re: [HACKERS] compiling source code!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Hi Sibel, Here's the mail that I posted about 10 days ago about compiling and debugging postgres on windows. I have used msys/mingw toolkit and it is the recommended (by pg community) toolkit to compile postgres on windows. http://archives.postgresql.org/pgsql-hackers/2006-05/msg00396.php

[HACKERS] Gborg and pgfoundry

I am asking again: what is the timetable for merging gborg and pgfoundry, and if not, can we set a date to shut down to force the move. -- Bruce Momjian http://candle.pha.pa.us EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +

Re: [HACKERS] timezones to own config file

Joachim Wieland <[EMAIL PROTECTED]> writes: > I'd like to know what exactly is to be done for this TODO-item > o Allow customization of the known set of TZ names (generalize the > present australian_timezones hack) Well, part of the TODO is to figure out exactly what to do ;-) > So we'd

Re: [HACKERS] v814 + OSX10.4.6 builds OK, but fails launch ...

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 >> /usr/local/pgsql/bin > ls -al postmaster >> lrwxrwx--- 1 root wheel 8 2006-05-24 07:48 postmaster -> postgres > > Hm, is it significant that that symlink is set for no access by world? hmmm, too. > I don't remember if Darwin enforces a

Re: [HACKERS] v814 + OSX10.4.6 builds OK, but fails launch ...

Richard <[EMAIL PROTECTED]> writes: >> Look at the postmaster -> postgres symlink; >> is it where it's supposed to be? > seems to be: > /usr/local/pgsql/bin > ls -al postmaster > lrwxrwx--- 1 root wheel 8 2006-05-24 07:48 postmaster -> postgres Hm, is it significant that that symlink is s

Re: [HACKERS] v814 + OSX10.4.6 builds OK, but fails launch ...

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 tom, >> v8.1.3 on all boxes. i can currently successfully (re)build 813 on this >> box now, with no such problems ... > > Curious. yup. I just rebuilt/tested CVS HEAD successfully on my own 10.4.6 > laptop ... good to know ... > I'll try R

Re: [HACKERS] v814 + OSX10.4.6 builds OK, but fails launch ...

Richard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 hi all, i've working built-from-source v813 installs on OSX 10.4.6. staring with a clean 814 src tree, a similarly-config'd build completes without error: % postmaster --version postmaster (PostgreSQL) 8.1.4

Re: [HACKERS] v814 + OSX10.4.6 builds OK, but fails launch ...

Richard <[EMAIL PROTECTED]> writes: >> If so, what was the last version that worked for you? > v8.1.3 on all boxes. i can currently successfully (re)build 813 on this > box now, with no such problems ... Curious. I just rebuilt/tested CVS HEAD successfully on my own 10.4.6 laptop ... I'll try R

Re: [HACKERS] v814 + OSX10.4.6 builds OK, but fails launch ...

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 hi tom, >> LOG: 0: could not read symbolic link "postmaster" >> LOCATION: resolve_symlinks, exec.c:338 >> FATAL: XX000: /usr/local/pgsql/bin/postmaster: could not locate my >> own executable path >> LOCATION: PostmasterMain, postm

[HACKERS] timezones to own config file

I'd like to know what exactly is to be done for this TODO-item o Allow customization of the known set of TZ names (generalize the present australian_timezones hack) The most recent mail in the archives about this subject seems to be: http://archives.postgresql.org/pgsql-general/2006-04

Re: [HACKERS] v814 + OSX10.4.6 builds OK, but fails launch ...

Richard <[EMAIL PROTECTED]> writes: > LOG: 0: could not read symbolic link "postmaster" > LOCATION: resolve_symlinks, exec.c:338 > FATAL: XX000: /usr/local/pgsql/bin/postmaster: could not locate my > own executable path > LOCATION: PostmasterMain, postmaster.c:435 > known? Nope, a

Re: [HACKERS] file-locking and postmaster.pid

korry <[EMAIL PROTECTED]> writes: > Isn't that sort of like saying that if a postmaster.pid file exists, it > must have been written by a postmaster? Pick a semaphore id and > dedicate it to postmaster exclusion. That's not workable, unless you want to assume that nothing on the system except P

[HACKERS] v814 + OSX10.4.6 builds OK, but fails launch ...

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 hi all, i've working built-from-source v813 installs on OSX 10.4.6. staring with a clean 814 src tree, a similarly-config'd build completes without error: % postmaster --version postmaster (PostgreSQL) 8.1.4 but, on executab

Re: [HACKERS] file-locking and postmaster.pid

> > > You never need to reduce it to a shared lock. On postmaster startup, > > > try to lock the sentinel byte (one byte past the end-of-file). If you > > > can lock it, you know that no other postmaster has that byte locked. If > > > you can't lock it, another postmaster is running. It is

Re: [HACKERS] file-locking and postmaster.pid

We already have two platforms that don't use the SysV semaphore interface, and even on ones that have it, I wouldn't want to assume they all support SEM_UNDO. Which platforms, just out of curiousity?  I assume that Win32 is one of them. But aside from any portability issues, ISTM this w

Re: [HACKERS] file-locking and postmaster.pid

Alvaro Herrera <[EMAIL PROTECTED]> writes: > Well, you are wrong here. We _want_ every backend to hold a shared > lock. We need to stop a postmaster from starting if there is a backend > running that was started by a no-longer-running postmaster. Note that we currently rely on checking for SysV

Re: [HACKERS] file-locking and postmaster.pid

korry wrote: > > > You never need to reduce it to a shared lock. On postmaster startup, > > > try to lock the sentinel byte (one byte past the end-of-file). If you > > > can lock it, you know that no other postmaster has that byte locked. If > > > you can't lock it, another postmaster is running

Re: [HACKERS] file-locking and postmaster.pid

korry <[EMAIL PROTECTED]> writes: >> Well, it fails in the safe direction: the postmaster may occasionally >> refuse to start when it should, but it won't ever start when it should >> not. It appears to me that anything relying on file locking will tend >> to fail in the other direction, and that'

Re: [HACKERS] file-locking and postmaster.pid

> You never need to reduce it to a shared lock. On postmaster startup, > try to lock the sentinel byte (one byte past the end-of-file). If you > can lock it, you know that no other postmaster has that byte locked. If > you can't lock it, another postmaster is running. It is an atomic > ope

Re: [HACKERS] file-locking and postmaster.pid

> What we currently have in place is not bulletproof. Well, it fails in the safe direction: the postmaster may occasionally refuse to start when it should, but it won't ever start when it should not. It appears to me that anything relying on file locking will tend to fail in the other direc

Re: [HACKERS] compiling source code!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

On Wed, May 24, 2006 at 01:46:19AM -0700, sibel karaasma wrote: > Hi I'm a new postgresql user. I wrote ACO (ant colony optimazition) and > want to replace it with GEQO in postres/src/backend/optimizer but I don't > know how > to compile and run the source code :( > > I installed postgresq

Re: [HACKERS] compiling source code!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

sibel karaasma schrieb: > Hi I'm a new postgresql user. I wrote ACO (ant colony optimazition) and > want to replace it with GEQO in postres/src/backend/optimizer but I > don't know how > to compile and run the source code :( > > I installed postgresql-8.1.3 and cygwin but I can not use them to

Re: [HACKERS] file-locking and postmaster.pid

korry <[EMAIL PROTECTED]> writes: > What we currently have in place is not bulletproof. Well, it fails in the safe direction: the postmaster may occasionally refuse to start when it should, but it won't ever start when it should not. It appears to me that anything relying on file locking will ten

Re: [HACKERS] Compression and on-disk sorting

On Wed, May 24, 2006 at 02:20:43PM -0700, Joshua D. Drake wrote: > Jim C. Nasby wrote: > >Finally completed testing of a dataset that doesn't fit in memory with > >compression enabled. Results are at > >http://jim.nasby.net/misc/pgsqlcompression . > > > >Summary: > >work_mem

Re: [HACKERS] file-locking and postmaster.pid

korry wrote: > > I think the next question is -- how would the lock interface be used? > > We could acquire an exclusive lock on postmaster start (to make sure no > > backend is running), then reduce it to a shared lock. Every backend > > would inherit the shared lock. But the lock exchange is n

Re: [HACKERS] file-locking and postmaster.pid

korry <[EMAIL PROTECTED]> writes: > However, Tom may be correct about NFS locking, but I guess I'm surprised > that anyone would care :-) Whether we think it's a real good idea or not, *plenty* of people run databases across NFS. We can't blow off that set of users. regar

Re: [HACKERS] file-locking and postmaster.pid

Andrew Dunstan wrote: > Alvaro Herrera wrote: > >Alvaro Herrera wrote: > > > >>Note that it may fail! This seems to indicate that some platforms do > >>not provide either locking mechanism. > > > >(Which means the whole discussion is a waste of time) > > Umm, no, I don't think so. It will block i

Re: [HACKERS] file-locking and postmaster.pid

Alvaro Herrera <[EMAIL PROTECTED]> writes: > Certainly on all platforms there must be *some* locking primitive. We > just need to figure out the appropiate parameters to fcntl() or flock() > or lockf() on each. I use lockf() (not fcntl() or flock()) on every platform other than Win32.  Of

Re: [HACKERS] file-locking and postmaster.pid

On Wed, 2006-05-24 at 16:34 -0400, Alvaro Herrera wrote: korry wrote: > > The Win32 API for locking seems mighty strange to me. > > Linux/Unix byte locking is advisory (meaning that one lock can block > another lock, but it can't block a read). No -- it is advisory meaning that a process t

Re: [HACKERS] Compression and on-disk sorting

Jim C. Nasby wrote: Finally completed testing of a dataset that doesn't fit in memory with compression enabled. Results are at http://jim.nasby.net/misc/pgsqlcompression . Summary: work_memcompressed not compressed gain in-memory 2 400.1 797.7

Re: [HACKERS] file-locking and postmaster.pid

Alvaro Herrera wrote: Alvaro Herrera wrote: Note that it may fail! This seems to indicate that some platforms do not provide either locking mechanism. (Which means the whole discussion is a waste of time) Umm, no, I don't think so. It will block instead of failing unless you r

Re: [HACKERS] Improving ALTER TYPE support

Ok, this way works and the proposed way isn't necessary. On 5/24/06, Tom Lane <[EMAIL PROTECTED]> wrote: "John Jawed" <[EMAIL PROTECTED]> writes: > I guess I don't understand what one has to do with the other (SRF's > returning records and OUT parameters). I always thought they were exclusive, >

Re: [HACKERS] file-locking and postmaster.pid

Alvaro Herrera wrote: > Note that it may fail! This seems to indicate that some platforms do > not provide either locking mechanism. (Which means the whole discussion is a waste of time) -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Cons

Re: [HACKERS] file-locking and postmaster.pid

Andrew Dunstan wrote: > We use file locking on Win32 (and on all other platforms) in the > buildfarm ... it's done from perl so maybe perl does some magic under > the hood. The call looks just the same, and works fine on W32, I > believe. It is roughly: > > use Fcntl qw(:flock); > open($lockf

Re: [HACKERS] Improving ALTER TYPE support

Tom, > If you write something like > > create function foo (in p1 int, out r1 int, out r2 text) > returns setof record D'oh! I feel like a dork now. I forgot we had this. -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco ---(end of broadcast)--

Re: [HACKERS] file-locking and postmaster.pid

Alvaro Herrera <[EMAIL PROTECTED]> writes: > Certainly on all platforms there must be *some* locking primitive. We > just need to figure out the appropiate parameters to fcntl() or flock() > or lockf() on each. Quite aside from the hassle factor of needing to deal with N variants of the syscalls,

Re: [HACKERS] file-locking and postmaster.pid

korry wrote: > > The Win32 API for locking seems mighty strange to me. > > Linux/Unix byte locking is advisory (meaning that one lock can block > another lock, but it can't block a read). No -- it is advisory meaning that a process that does not try to acquire the lock is not locked out. You ca

Re: [HACKERS] file-locking and postmaster.pid

Alvaro Herrera wrote: korry wrote: The only platform (although certainly not a minor issue) that I can think of that would have a portability issue would be Win32. You can't even read a locked byte in Win32. I usually solve that problem by locking a byte past the end of the file (which is p

Re: [HACKERS] file-locking and postmaster.pid

Certainly on all platforms there must be *some* locking primitive. We just need to figure out the appropiate parameters to fcntl() or flock() or lockf() on each. Right. The Win32 API for locking seems mighty strange to me. Linux/Unix byte locking is advisory (meaning that one lo

Re: [HACKERS] Compression and on-disk sorting

Finally completed testing of a dataset that doesn't fit in memory with compression enabled. Results are at http://jim.nasby.net/misc/pgsqlcompression . Summary: work_memcompressed not compressed gain in-memory 2 400.1 797.7 49.8% in-mem

Re: [HACKERS] error-free disabling of individual child partition

On Wed, 2006-05-24 at 09:40 -0400, Tom Lane wrote: > Simon Riggs <[EMAIL PROTECTED]> writes: > > On Wed, 2006-05-24 at 11:17 +0300, Hannu Krosing wrote: > >> Why "never set back again" ? I'd guess that it should be set back to > >> true when it is not an inherited column anymore, that is when its >

Re: [HACKERS] Improving ALTER TYPE support

"John Jawed" <[EMAIL PROTECTED]> writes: > I guess I don't understand what one has to do with the other (SRF's > returning records and OUT parameters). I always thought they were exclusive, > could you elaborate? (BTW, please don't post uselessly HTML-ified mail.) If you write something like

Re: [HACKERS] file-locking and postmaster.pid

korry wrote: > The only platform (although certainly not a minor issue) that I can > think of that would have a portability issue would be Win32. You can't > even read a locked byte in Win32. I usually solve that problem by > locking a byte past the end of the file (which is portable). Certainly

Re: [HACKERS] file-locking and postmaster.pid

On Wednesday 24 May 2006 21:03, korry wrote: > > I'm sure there's a good reason for having it the way it is, having so > > many smart knowledgeable people working on this project. Could someone > > please explain the rationale of the current solution to me? > > We've ignored Andreas' original

Re: [HACKERS] file-locking and postmaster.pid

I'm sure there's a good reason for having it the way it is, having so many smart knowledgeable people working on this project. Could someone please explain the rationale of the current solution to me? We've ignored Andreas' original question.  Why not use a lock to indicate that the po

Re: [HACKERS] file-locking and postmaster.pid

On Wednesday 24 May 2006 20:52, Andrej Ricnik-Bay wrote: > On 5/24/06, Andreas Joseph Krogh <[EMAIL PROTECTED]> wrote: > > > My PG is not started with startup-scripts, but with this command: > > > > > > pg_ctl -D $PGDATA -l $PGDIR/log/logfile-`date +%Y-%m-%d`.log start > > > > ... and manually afte

Re: [HACKERS] file-locking and postmaster.pid

On Wednesday 24 May 2006 21:03, korry wrote: > > I'm sure there's a good reason for having it the way it is, having so > > many smart knowledgeable people working on this project. Could someone > > please explain the rationale of the current solution to me? > > We've ignored Andreas' original quest

Re: [HACKERS] Further reduction of bufmgr lock contention

Josh Berkus writes: > BTW, we're going to be testing this patch on Sun Niagara servers. What's > the outstanding bug with it? I don't quite follow. It's not acceptable as-is because of the risk of running out of shared memory for hashtable entries. In the existing code, there's a clear uppe

Re: [HACKERS] Why is CVS server so slow?

> >> On Tue, May 23, 2006 at 08:30:36PM -0300, Marc G. Fournier wrote: > >>> I'm logged on daily interactively, and haven't noticed > any issues ... > > > >> Are you both referring to the same server? I've noticed that > >> anoncvs.postgresql.org (66.98.251.159) has been slow for a > couple of

Re: [HACKERS] Why is CVS server so slow?

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Marc > G. Fournier > Sent: 24 May 2006 20:06 > To: Tom Lane > Cc: Michael Fuhr; Simon Riggs; pgsql-hackers@postgresql.org > Subject: Re: [HACKERS] Why is CVS server so slow? > > Anyone noticing an

Re: [HACKERS] problem with PQsendQuery/PQgetResult and COPY FROM statement

[EMAIL PROTECTED] writes: > I do not expect PQgetResult to return millions of non-null PGresult > objects after a PQsendQuery("COPY test FROM STDIN"). I expect exactly > one non-null result, with a result status of PGRES_COPY_IN. If you call it exactly once, it'll say that exactly once. If you k

Re: [HACKERS] Why is CVS server so slow?

On Tue, 23 May 2006, Tom Lane wrote: Michael Fuhr <[EMAIL PROTECTED]> writes: On Tue, May 23, 2006 at 08:30:36PM -0300, Marc G. Fournier wrote: I'm logged on daily interactively, and haven't noticed any issues ... Are you both referring to the same server? I've noticed that anoncvs.postgre

Re: [HACKERS] Improving ALTER TYPE support

I guess I don't understand what one has to do with the other (SRF's returning records and OUT parameters). I always thought they were exclusive, could you elaborate?On 5/24/06, Tom Lane <[EMAIL PROTECTED]> wrote: Josh Berkus writes:>> I've been working on a function which retu

Re: [HACKERS] Further reduction of bufmgr lock contention

Tom, BTW, we're going to be testing this patch on Sun Niagara servers. What's the outstanding bug with it? I don't quite follow. I think I can get some of the Sun MDEs to take a stab at it if I can understand the issue. Links ok if maybe I've not found part of this thread in the archives.

Re: [HACKERS] file-locking and postmaster.pid

On 5/24/06, Andreas Joseph Krogh <[EMAIL PROTECTED]> wrote: > My PG is not started with startup-scripts, but with this command: > > pg_ctl -D $PGDATA -l $PGDIR/log/logfile-`date +%Y-%m-%d`.log start ... and manually after login, ie. not at boot-time. I'd suggest trying to fix your Linux-instal

Re: [HACKERS] Updatable views/with check option parsing

Peter Eisentraut <[EMAIL PROTECTED]> writes: > I have spent some time figuring out how to resolve the parsing conflicts in > Bernd Helmle's updatable views patch. The problem has now been reduced to > specifically this situation: Could we see the proposed patches for gram.y? > If we can't get

Re: [HACKERS] error-free disabling of individual child partition

Alvaro Herrera <[EMAIL PROTECTED]> writes: > Hannu Krosing wrote: >> I don't think that LIKE inheritance is inheritance at all, rather it is >> a create-time macro. > In that case the columns should be marked attislocal. Right. regards, tom lane -

Re: [HACKERS] error-free disabling of individual child partition

Hannu Krosing wrote: I don't think that LIKE inheritance is inheritance at all, rather it is a create-time macro. Right. It's actually quite useful. I'd like to see it made available in a couple of other contexts, such as CREATE TYPE and the type expression needed when calling a functio

Re: [HACKERS] error-free disabling of individual child partition

Hannu Krosing wrote: > Ühel kenal päeval, K, 2006-05-24 kell 09:40, kirjutas Tom Lane: > > Simon Riggs <[EMAIL PROTECTED]> writes: > > > On Wed, 2006-05-24 at 11:17 +0300, Hannu Krosing wrote: > > >> Why "never set back again" ? I'd guess that it should be set back to > > >> true when it is not an

Re: [HACKERS] error-free disabling of individual child partition

Ühel kenal päeval, K, 2006-05-24 kell 09:40, kirjutas Tom Lane: > Simon Riggs <[EMAIL PROTECTED]> writes: > > On Wed, 2006-05-24 at 11:17 +0300, Hannu Krosing wrote: > >> Why "never set back again" ? I'd guess that it should be set back to > >> true when it is not an inherited column anymore, that

Re: [HACKERS] Updatable views/with check option parsing

Hannu Krosing wrote: Can't we teach tokenized a new token "WITH TIME ZONE" ? No, that's three tokens, not one. We surely don't want to start making white space significant. cheers andrew ---(end of broadcast)--- TIP 6: explain analyze is

Re: [HACKERS] Improving ALTER TYPE support

Josh Berkus writes: >> I've been working on a function which returns a setof a composite type. >> Everytime I've changed the structure of the returning setof, I've had to >> change the type accordingly, which current means doing a drop type ... >> cascade down to the function. We should allow one

Re: [HACKERS] error-free disabling of individual child partition

Simon Riggs <[EMAIL PROTECTED]> writes: > On Wed, 2006-05-24 at 11:17 +0300, Hannu Krosing wrote: >> Why "never set back again" ? I'd guess that it should be set back to >> true when it is not an inherited column anymore, that is when its >> attinhcount reaches zero. > Because you have no record o

Re: [HACKERS] error-free disabling of individual child partition

On Wed, 2006-05-24 at 11:17 +0300, Hannu Krosing wrote: > Ühel kenal päeval, T, 2006-05-23 kell 18:48, kirjutas Simon Riggs: > > > > > 2. attislocal is always set False when an appropriate ADD INHERITS is > > actioned. Not ever set back again. > > Why "never set back again" ? I'd guess that it s

Re: [HACKERS] problem with PQsendQuery/PQgetResult and COPY FROM statement

Thanks for all your replies, but I must clarify some things. First, note that what I posted is just a small example that reproduces behavior that appears incorrect. The real code is a C++ wrapper around libpq that supports non-blocking queries and reuses open connections. Volkan and Martijn: I k

Re: [HACKERS] Updatable views/with check option parsing

Ühel kenal päeval, K, 2006-05-24 kell 13:13, kirjutas Peter Eisentraut: > I have spent some time figuring out how to resolve the parsing conflicts in > Bernd Helmle's updatable views patch. The problem has now been reduced to > specifically this situation: > > CREATE VIEW foo AS SELECT expr ::

[HACKERS] Updatable views/with check option parsing

I have spent some time figuring out how to resolve the parsing conflicts in Bernd Helmle's updatable views patch. The problem has now been reduced to specifically this situation: CREATE VIEW foo AS SELECT expr :: TIME . WITH (where expr is a_expr or b_expr and TIME could also be TIMESTAMP or T

Re: [HACKERS] file-locking and postmaster.pid

On Wednesday 24 May 2006 11:36, Andreas Joseph Krogh wrote: > On Tuesday 23 May 2006 19:36, Tom Lane wrote: > > Adis Nezirovic <[EMAIL PROTECTED]> writes: > > > Well, maybe you could tweak postgres startup script, add check for post > > > master (either 'pgrep postmaster' or 'ps -axu | grep [p]ostm

Re: [HACKERS] file-locking and postmaster.pid

On Tuesday 23 May 2006 19:36, Tom Lane wrote: > Adis Nezirovic <[EMAIL PROTECTED]> writes: > > Well, maybe you could tweak postgres startup script, add check for post > > master (either 'pgrep postmaster' or 'ps -axu | grep [p]ostmaster'), and > > delete pid file on negative results. > > This is ex

[HACKERS] compiling source code!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Hi I'm a new postgresql user. I wrote ACO (ant colony optimazition) and want to replace it with GEQO in postres/src/backend/optimizer but I don't know how to compile and run the source code :(     I installed postgresql-8.1.3 and cygwin but I can not use them to compile the source code. I want to c

Re: [HACKERS] LIKE, leading percent, bind parameters and indexes

> AFAICS the problem is not restricted to LIKE, we can easily find a lot of > similar problems caused by the actual parameters. For example, SeqScan vs. > IndexScan vs. BitmapIndexScan for a range query. So an improvement is > definitely needed. > Another way is to generate a plan on the fly. What

Re: [HACKERS] error-free disabling of individual child partition

Ühel kenal päeval, T, 2006-05-23 kell 18:48, kirjutas Simon Riggs: > > 2. attislocal is always set False when an appropriate ADD INHERITS is > actioned. Not ever set back again. Why "never set back again" ? I'd guess that it should be set back to true when it is not an inherited column anymore,

Re: [HACKERS] Further reduction of bufmgr lock contention

Tom Lane wrote: We're certainly not putting any such thing into 8.1.*. The proposed patch for 8.2 is stalled ATM because of the problem of not having a predictable size for the per-partition hash tables. Fixed-size shared memory is a harsh mistress :-( Fair enough :) Just wanted to ascertai

Re: [HACKERS] error-free disabling of individual child partition

Ühel kenal päeval, K, 2006-05-24 kell 09:56, kirjutas Zeugswetter Andreas DCP SD: > > Added to TODO: > > > > o Add ALTER TABLE tab ADD/DROP INHERITS parent > > Sounds good, more inline with add/drop constraint. > > > pg_attribute.attislocal has to be set to 'false' for ADD, > a

Re: [HACKERS] error-free disabling of individual child partition

> Added to TODO: > > o Add ALTER TABLE tab ADD/DROP INHERITS parent Sounds good, more inline with add/drop constraint. > pg_attribute.attislocal has to be set to 'false' for ADD, and >> attislocal: If you set this to False, you wouldn't be able to set it >> back again. Just c