[HACKERS] Socket problem using beta2 on Windows-XP

Hi, I've installed PostgreSQL 8.1-beta2 as a service on my Windows-XP box. It runs fine but I get repeated messages like this in the log: 2005-09-29 00:41:09 FATAL: could not duplicate socket 1880 for use in backend: error code 10038 and for each message printed, a new postgres process is

Re: [HACKERS] [DOCS] Added documentation about caching, reliability

Am Mittwoch, 28. September 2005 20:26 schrieb Bruce Momjian: > I also renamed the chapter "Reilability" rather than "WAL." Considering that the chapter is, in fact, all about WAL, I don't think this is a good move. Reliability is a concern that is not only addressed by the WAL system. Please c

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Am Mittwoch, 28. September 2005 18:10 schrieb Bruce Momjian: > If it was that bad, we should have fixed it during development, not > during beta. The only reason it is getting attention now is because it > is triggered more by a new feature we are adding, a feature we can > easily remove. That wa

Re: [HACKERS] Server process exited with unexpected status 128.

Tom Lane wrote: Is it sensible to try to prevent people from raising the GUC variable higher than the platform will allow? It seems we can know the limit on Windows, but on most other platforms I don't think there's any good way to find it out. (Which is why max_stack_depth is a SUSET variable

Re: [HACKERS] [PERFORM] A Better External Sort?

On Wed, 2005-09-28 at 12:03 -0400, Ron Peacetree wrote: > >From: "Jeffrey W. Baker" <[EMAIL PROTECTED]> > >Sent: Sep 27, 2005 1:26 PM > >To: Ron Peacetree <[EMAIL PROTECTED]> > >Subject: Re: [HACKERS] [PERFORM] A Better External Sort? > > > >On Tue, 2005-09-27 at 13:15 -0400, Ron Peacetree wrote: >

[HACKERS] pg_total_relation_size() could not open relation with OID X

Here's a test case for a pg_total_relation_size() failure: test=> CREATE TABLE foo (id integer); CREATE TABLE test=> SELECT oid, relfilenode FROM pg_class WHERE relname = 'foo'; oid | relfilenode ---+- 26235 | 26235 (1 row) test=> SELECT pg_total_relation_size('foo');

[HACKERS] Open items list

Here is the open item list: > >PostgreSQL 8.1 Open Items >= > > Current version at http://candle.pha.pa.us/cgi-bin/pgopenitems or > from http://www.postgresql.org/developer/beta. > > Bugs > > fix pg_dum

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Also, why is the nextval ::text casting output by pg_dump anyway? --- Tom Lane wrote: > Bruce Momjian writes: > > I am thinking we should hard-code something in the backend so if the > > function oid is nextval/currval/setv

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Tom Lane wrote: > Bruce Momjian writes: > > I am thinking we should hard-code something in the backend so if the > > function oid is nextval/currval/setval, we strip off any text casting > > internally. > > NO. No bloody way ... that is far dirtier than any other proposal > that's been made in t

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Bruce Momjian writes: > I am thinking we should hard-code something in the backend so if the > function oid is nextval/currval/setval, we strip off any text casting > internally. NO. No bloody way ... that is far dirtier than any other proposal that's been made in this thread. I don't even want

Re: [HACKERS] [DOCS] Added documentation about caching, reliability

Alvaro Herrera wrote: > On Wed, Sep 28, 2005 at 10:08:02PM -0400, Bruce Momjian wrote: > > > The chapter sections are: > > > > Table of Contents > > 26.1. Write-Ahead Logging (WAL) > > 26.2. Benefits of WAL > > 26.3. WAL Configuration > > 26.4. WAL Internals > > > > Are you s

Re: [HACKERS] [DOCS] Added documentation about caching, reliability

On Wed, Sep 28, 2005 at 10:08:02PM -0400, Bruce Momjian wrote: > The chapter sections are: > > Table of Contents > 26.1. Write-Ahead Logging (WAL) > 26.2. Benefits of WAL > 26.3. WAL Configuration > 26.4. WAL Internals > > Are you suggesting we spell out Write-Ahead

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Just to summarize, I am arguing from a usability perspective, because I believe the simplest API is one that will last for many releases and not have to be redesigned, nor require too much adjustment from our users. --- Bruc

Re: [HACKERS] Open items list for 8.1

Bruce Momjian writes: > It was done quickly to complete it for beta2. Neil talked to Tom and me > about it before he made the change. Obviously we all guessed wrong on > this one. Personally I had forgotten that pg_cancel_backend was in the previous release and so there was a backwards-compatibi

Re: [HACKERS] Found small issue with OUT params

Tom Lane wrote: > Tony Caduto <[EMAIL PROTECTED]> writes: > > Please don't take this the wrong way, but don't you think even if a > > single param is declared as OUT it should return the name of the OUT param? > > Not really, because "create function foo (in x int, out y float)" is > supposed to

Re: [HACKERS] [DOCS] Added documentation about caching, reliability

IMHO, spelling out each one is redundant... the first one "Write-Ahead Logging (WAL)" seems to define WAL for use later in the text. On 9/28/05, Bruce Momjian wrote: Alvaro Herrera wrote:> On Wed, Sep 28, 2005 at 02:26:24PM -0400, Bruce Momjian wrote:> > I have added a sect

Re: [HACKERS] [DOCS] Added documentation about caching, reliability

Alvaro Herrera wrote: > On Wed, Sep 28, 2005 at 02:26:24PM -0400, Bruce Momjian wrote: > > I have added a section to the top of the WAL docs explaining caching and > > reliability issues: > > > > http://candle.pha.pa.us/main/writings/pgsql/sgml/reliability.html > > > > I also renamed the chap

Re: [HACKERS] Found small issue with OUT params

Tony Caduto <[EMAIL PROTECTED]> writes: > Please don't take this the wrong way, but don't you think even if a > single param is declared as OUT it should return the name of the OUT param? Not really, because "create function foo (in x int, out y float)" is supposed to have the same external behav

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Tom Lane wrote: > Bruce Momjian writes: > > I am thinking we need to have nextval('') do early binding and have > > nextval(''::text) (or some other name) do late binding. > > You can't have that in exactly that form, because text is invariably > the preferred resolution of unknown-type literals,

Re: [HACKERS] Open items list for 8.1

Marc G. Fournier wrote: > On Tue, 27 Sep 2005, Bruce Momjian wrote: > > > Tom Lane wrote: > >> Bruce Momjian writes: > >>> fix ALTER SCHEMA RENAME for sequence dependency, or remove feature > >> > >> I've posted a proposed patch to fix this. The patch requires an initdb > >> (to add new sequence

Re: [HACKERS] postgresql clustering

Gaetano Mendola wrote: Daniel Duvall wrote: I've looked at PostgreSQL and EnterpriseDB, but I can't find anything definitive as far as clustering capabilities. What kinds of projects are there for clustering PgSQL, and are any of them mature enough for commercial apps? Are you look

Re: [HACKERS] postgresql clustering

Daniel Duvall wrote: > I've looked at PostgreSQL and EnterpriseDB, but I can't find anything > definitive as far as clustering capabilities. What kinds of projects > are there for clustering PgSQL, and are any of them mature enough for > commercial apps? As you well know "clustering" means all

Re: [HACKERS] enhanced pgbench

> Tatsuo Ishii <[EMAIL PROTECTED]> writes: > > 2) it requires a location where those scripts reside. $prefix/etc > >seems appropriate? > > I was thinking of just embedding the default scripts as constants in > the program text. A little bit ugly but saves a lot of headache with > needing to f

Re: [HACKERS] Found small issue with OUT params

Tom Lane wrote: Tony Caduto <[EMAIL PROTECTED]> writes: If I call it like this: select * from FIND_USER_SOCKET_BYNAME('juser'); I would expect to get back 1 value with the name of the OUT param (OUT_SOCKET_ADDRESS). However it comes back with the name of the function This is intenti

Re: [HACKERS] Open items list for 8.1

On Wed, 2005-28-09 at 18:35 -0300, Marc G. Fournier wrote: > The problem isn't whether or not they should be changed, the problem is > that they were changed *during* beta AND *against* the direction that > discussion on these changes went I'm not sure what you mean: what is "the direction that

Re: [HACKERS] execution of prepared statements leaks memory

Dmitry Karasik <[EMAIL PROTECTED]> writes: > I'm not sure whether I've stumbled over a bug or a feature, so I'm > curious if someone might explain that. It's a bug --- _SPI_execute_plan isn't handling the possibility that a utility command could create a tupletable that could be passed back to the

Re: [HACKERS] Vacuum questions...

On T, 2005-09-27 at 17:57 -0500, Jim C. Nasby wrote: > On Tue, Sep 27, 2005 at 02:47:46PM -0400, Jan Wieck wrote: > > On 9/24/2005 8:17 PM, Jim C. Nasby wrote: > > > > >Would it be difficult to vacuum as part of a dump? The reasoning behind > > >this is that you have to read the table to do the du

Re: [HACKERS] Open items list for 8.1

On Tue, 27 Sep 2005, Bruce Momjian wrote: Tom Lane wrote: Bruce Momjian writes: fix ALTER SCHEMA RENAME for sequence dependency, or remove feature I've posted a proposed patch to fix this. The patch requires an initdb (to add new sequence functions), so if we do that we may as well also fi

Re: [HACKERS] effective SELECT from child tables

On Wed, Sep 28, 2005 at 11:00:46PM +0400, Ilia Kantor wrote: > Your suggestion is essentially the same as mine.. > There exists tableoid, pretty much suited to tell between tables in the case > of inheritance.. I can't see a "real" need to add a special "class > classifier" to each table.. > This

Re: [HACKERS] [DOCS] Added documentation about caching, reliability

On Wed, Sep 28, 2005 at 02:26:24PM -0400, Bruce Momjian wrote: > I have added a section to the top of the WAL docs explaining caching and > reliability issues: > > http://candle.pha.pa.us/main/writings/pgsql/sgml/reliability.html > > I also renamed the chapter "Reilability" rather than "WAL

Re: [HACKERS] Found small issue with OUT params

Tony Caduto <[EMAIL PROTECTED]> writes: > If I call it like this: > select * from FIND_USER_SOCKET_BYNAME('juser'); > I would expect to get back 1 value with the name of the OUT param > (OUT_SOCKET_ADDRESS). > However it comes back with the name of the function This is intentional, for compatibi

[HACKERS] Found small issue with OUT params

Hi, consider this function: CREATE OR REPLACE FUNCTION FIND_USER_SOCKET_BYNAME ( IN IN_USERNAME VARCHAR, OUT OUT_SOCKET_ADDRESS INTEGER) AS $BODY$ BEGIN select socket_address from userdata where fullname = in_username into out_socket_address; if out_socket_address is nu

Re: [HACKERS] effective SELECT from child tables

> If you treat the sub-class Discriminator as a data item rather than some > additional syntax for class membership then you will find this works > very straightforwardly for you. Your suggestion is essentially the same as mine.. There exists tableoid, pretty much suited to tell between tables

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Bruce Momjian writes: > I am thinking we need to have nextval('') do early binding and have > nextval(''::text) (or some other name) do late binding. You can't have that in exactly that form, because text is invariably the preferred resolution of unknown-type literals, and we certainly dare not t

Re: [HACKERS] Added documentation about caching, reliability

Thanks, fixed. --- Jonah H. Harris wrote: > Hey Bruce, > > One grammar issue... otherwise great work. > > they can be moved to another computer with similar hardware and all > committed transaction will remain intact. > >

Re: [HACKERS] Added documentation about caching, reliability

Hey Bruce, One grammar issue... otherwise great work. they can be moved to another computer with similar hardware and all committed transaction will remain intact. should be they can be moved to another computer with similar hardware and all committed transactions will remain intact.On

Re: [HACKERS] effective SELECT from child tables

On Wed, 2005-09-28 at 12:13 +0400, Ilia Kantor wrote: > >> Let table A be inherited by A1, A2, A3. > >> How to select from A records where actual relations are A1, A2 ? > > >Why not just select directly from the child tables? I can't get excited > >about optimizing the case you propose. > > Beca

[HACKERS] Added documentation about caching, reliability

I have added a section to the top of the WAL docs explaining caching and reliability issues: http://candle.pha.pa.us/main/writings/pgsql/sgml/reliability.html I also renamed the chapter "Reilability" rather than "WAL." -- Bruce Momjian| http://candle.pha.pa.us

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Tom Lane wrote: > Bruce Momjian writes: > > Tom Lane wrote: > >> The more I think about it, the more I think that two sets of function > >> names might not be such an awful idea. next_value(), curr_value(), and > >> set_value() seem like they'd work well enough. Then we'd just say that > >> next

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Bruce Momjian writes: > Tom Lane wrote: >> The more I think about it, the more I think that two sets of function >> names might not be such an awful idea. next_value(), curr_value(), and >> set_value() seem like they'd work well enough. Then we'd just say that >> nextval and friends are deprecat

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Bruce Momjian writes: > Michael Paesold wrote: >> Since the NEXT VALUE FOR syntax has a special meaning, would it be better to >> support the oracle-style syntax sequence.nextval for now (and use the >> ::regclass for this)? I am not sure how easy that is considering >> schema.sequence.nextval.

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Michael Paesold wrote: > Tom Lane wrote: > > However, we could certainly add the NEXT VALUE FOR syntax if that will > > satisfy your concern about syntax. > > Since the NEXT VALUE FOR syntax has a special meaning, would it be better to > support the oracle-style syntax sequence.nextval for now (a

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Tom Lane wrote: However, we could certainly add the NEXT VALUE FOR syntax if that will satisfy your concern about syntax. Since the NEXT VALUE FOR syntax has a special meaning, would it be better to support the oracle-style syntax sequence.nextval for now (and use the ::regclass for this)? I

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Tom Lane wrote: > Bruce Momjian writes: > > I still think we shouldn't be hashing this out during beta, but ... > > We're looking at ways to fix some bugs. It's never been the case that > our first-resort response to a bug is "pull out features". True, but your first guess was that none of this

Re: [HACKERS] unchecked malloc

Sibtay Abbas <[EMAIL PROTECTED]> writes: > in pl_comp.c, plpgsql_build_variable takes a pointer to a PLpgSQL_type > structure, which is always a malloc'ed instance(since we always use > plpgsql_build_datatype function). As of current sources it's palloc'd, and should be released if the function is

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Tom Lane wrote: > Bruce Momjian writes: > > Just to follow up, I agree we can't totally replace all instances of > > nextval() with regclass because regclass requires a constant string, but > > I would like to have the regclass behavior with simple syntax and > > require people who want "late bind

Re: [HACKERS] Database file compatability

"William ZHANG" <[EMAIL PROTECTED]> wrote > > sizeof(int) maybe 8, but not 64. > And the configure option `--enable-integer-datetimes' may affect the data > layout. > Yes, typo. This has been checked by ControlFileData.enableIntTimes. Regards, Qingqing ---(end of broa

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Bruce Momjian writes: > Just to follow up, I agree we can't totally replace all instances of > nextval() with regclass because regclass requires a constant string, but > I would like to have the regclass behavior with simple syntax and > require people who want "late binding" of the sequence name

Re: [HACKERS] enhanced pgbench

Tatsuo Ishii <[EMAIL PROTECTED]> writes: > 2) it requires a location where those scripts reside. $prefix/etc >seems appropriate? I was thinking of just embedding the default scripts as constants in the program text. A little bit ugly but saves a lot of headache with needing to find installed

Re: [HACKERS] \d on database with a lot of tables is slow

"Jim C. Nasby" <[EMAIL PROTECTED]> writes: > Sorry, remembered it wrong. It's 'Did not find any relation named', > which appears to be in bin/psql/describe.c. It does occur when trying to > do a \d on a specific table. Hmm, no immediate ideas. You haven't provided a lot of context about this ---

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Tom Lane wrote: > > It is > > only the last one where recommending regclass helps, but is it worth > > improving sequence/schema renaming by exposing and recommending a > > ::regclass syntax that will go away as soon as we fix this properly? > > Please explain what you think a "proper" fix is. I

Re: [HACKERS] enhanced pgbench

> Tatsuo Ishii <[EMAIL PROTECTED]> writes: > > I think the enhanced pgbench is quite usefull and I would like to > > include in 8.1. Or should I keep it for 8.2? > > Well, we've traditionally been laxer about contrib than the core > software, so the fact that we're past feature freeze isn't suffic

Re: [HACKERS] Database file compatability

"Qingqing Zhou" <[EMAIL PROTECTED]> wrote > > "Tom Lane" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > > > There are no platforms for which ALIGNOF_SHORT is different from 2. > > I don't think there are any platforms we care about where ALIGNOF_INT > > is different from 4. The

Re: [HACKERS] [PATCHES] Proposed patch for sequence-renaming problems

Tom Lane wrote: > Bruce Momjian writes: > > What I am primarily worried about in your patch is the exposure of > > ::regclass as a recommended way of doing things. I know we can > > discourage its us later, but once people start using something, it is > > hard to change. > > Why shouldn't it be

Re: [HACKERS] Database file compatability

"Qingqing Zhou" <[EMAIL PROTECTED]> writes: > "Tom Lane" <[EMAIL PROTECTED]> wrote in message > There is a possible sequence like this: > ALIGNOF_LONG4 > ALIGNOF_DOUBLE 8 > MAXIMUM_ALIGNOF 8 > vs. > ALIGNOF_LONG8 > ALIGNOF_DOUBLE 8 > MAXIMUM_ALIGNOF 8 > So we

Re: [HACKERS] enhanced pgbench

Tatsuo Ishii <[EMAIL PROTECTED]> writes: > I think the enhanced pgbench is quite usefull and I would like to > include in 8.1. Or should I keep it for 8.2? Well, we've traditionally been laxer about contrib than the core software, so the fact that we're past feature freeze isn't sufficient reason

Re: [HACKERS] Making pgxs builds work with a relocated installation

Alvaro Herrera <[EMAIL PROTECTED]> writes: > The only question is, do we want to force a Python dependency for > building Postgres? That's not happening. Especially not now that Dave found the other solution does work ... regards, tom lane ---(end

Re: [HACKERS] effective SELECT from child tables

On Tue, Sep 27, 2005 at 09:30:55PM +0400, Ilia Kantor wrote: > Let table A be inherited by A1, A2, A3. > How to select from A records where actual relations are A1, A2 ? If A1 and A2 will be naturally together, where compared to A, or A3, why not introduce an intermediate table? A would be inheri

Re: [HACKERS] Making pgxs builds work with a relocated installation

On Wed, Sep 28, 2005 at 10:05:48AM +0100, Dave Page wrote: > > Tom Lane wrote: > > > Yuck. Anyone have another idea on coping with space-containing > > > pathnames? > > > > Switch to scons. You heard it here first! > > Oooh, that looks nice at first glance... The only question is, do we want

Re: [HACKERS] [PERFORM] PostgreSQL overall design

On 9/27/05, Bruce Momjian wrote: Have you read the developers FAQ? Thanks Bruce. I'm going through that. --- Gnanavel S wrote:> Hi All,>> Can anyone please tell/point me where I can get the postgresql s

Re: [HACKERS] [PERFORM] A Better External Sort?

>From: Josh Berkus >ent: Sep 27, 2005 12:15 PM >To: Ron Peacetree <[EMAIL PROTECTED]> >Subject: Re: [HACKERS] [PERFORM] A Better External Sort? > >I've somehow missed part of this thread, which is a shame since this is >an area of primary concern for me. > >Your suggested algorithm seems to be d

Re: [HACKERS] PostgreSQL overall design

On 9/27/05, Jonah H. Harris <[EMAIL PROTECTED]> wrote: Were you looking for a call graph? Yes. I want to know the list and sequence of files involved during  a call. On 9/27/05, Abhijit Menon-Sen <[EMAIL PROTECTED]> wrote: At 2005-09-27 15:20:05 +0530, [EMAIL PROTECTED] wrote:>> Can anyone please

Re: [HACKERS] PostgreSQL overall design

On 9/27/05, Andrew Dunstan <[EMAIL PROTECTED]> wrote: [ -performance removed ]Gnanavel S wrote:>>  Need a clarification in copydir.c file of src/port directory,  In the> following snippet the destination directory is created first then the > source directory is read. Suppose if I don't have permiss

Re: [HACKERS] Patching dblink.c to avoid warning about open transaction

Joe Conway wrote: Bruce Momjian wrote: [ Joe, would you review this? ] 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. The pa

Re: [HACKERS] [PERFORM] A Better External Sort?

I can't help wondering how a couple thousand context switches per second would affect the attempt to load disk info into the L1 and L2 caches. That's pretty much the low end of what I see when the server is under any significant load. ---(end of broadcast)---

Re: [HACKERS] Making pgxs builds work with a relocated installation

> -Original Message- > From: Tom Lane [mailto:[EMAIL PROTECTED] > Sent: 27 September 2005 18:57 > To: Magnus Hagander > Cc: Dave Page; Peter Eisentraut; pgsql-hackers@postgresql.org > Subject: Re: [HACKERS] Making pgxs builds work with a > relocated installation > > "Magnus Hagander"

[HACKERS] execution of prepared statements leaks memory

Hi, I'm not sure whether I've stumbled over a bug or a feature, so I'm curious if someone might explain that. The statement below declares a stored procedure: CREATE LANGUAGE PLPGSQL; DROP TABLE memleak_test; CREATE TABLE memleak_test (id serial); CREATE OR REPLACE FUNCTION memleak(INTEGER) RET

Re: [HACKERS] Making pgxs builds work with a relocated installation

> -Original Message- > From: Peter Eisentraut [mailto:[EMAIL PROTECTED] > Sent: 28 September 2005 06:37 > To: Tom Lane > Cc: Magnus Hagander; Dave Page; pgsql-hackers@postgresql.org > Subject: Re: [HACKERS] Making pgxs builds work with a > relocated installation > > Tom Lane wrote: >

Re: [HACKERS] effective SELECT from child tables

>> Let table A be inherited by A1, A2, A3. >> How to select from A records where actual relations are A1, A2 ? >Why not just select directly from the child tables? I can't get excited >about optimizing the case you propose. Because "WHERE concrete_class IN (a,b,c)" is much more convenient and f

Re: [HACKERS] effective SELECT from child tables

>> Maybe new constraint_exclusion staff could help to exclude non-matching >> tables from inheritance query ? > Yes, that's exactly what it's for. Your testing is welcome. Download 8.1 > and try it today. Great, I'm developing on 8.1b2 now... But could you be more particular about the soluti

Re: [HACKERS] Open items list for 8.1

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Marc > G. Fournier > Sent: 28 September 2005 00:50 > To: Tom Lane > Cc: Bruce Momjian; PostgreSQL-development; Neil Conway > Subject: Re: [HACKERS] Open items list for 8.1 > > > IMHO, changes lik