Andrew Overholt writes:
> [EMAIL PROTECTED] postgresql]$ time make all > make.nonsmp
> mkdir man7
>
>
> Should the man directory creation be echoed like that?
Yes, that appears to be normal.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: 05 November 2003 00:53
> To: PostgreSQL-development
> Subject: Re: [HACKERS] Open Sourcing pgManage
>
>
>
> Andreas Pflug wrote:
> > pgAdmin is designed for a good interactive experience, which isn't
> > a
On Tue, Nov 04, 2003 at 04:52:33PM -0500, Tom Lane wrote:
> Alexey Mahotkin <[EMAIL PROTECTED]> writes:
> > I'm running Postgresql 7.3.4 with ru_RU.UTF-8 locale (with UNICODE
> > database encoding), and all is almost well, except that UPPER() and
> > LOWER() seem to ignore locale.
>
> upper/lower
Hi all,
This is my first patch for PostgreSQL against the 7.5devel cvs (please advise if this
is the wrong place to post patches). This patch simply enables the \xDD (or \XDD)
hexadecimal import in the copy command (im starting with the simple stuff first). I
did notice that there may be a ne
Greg Stark wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
I think there is room for lots of GUIs, though, and having a Java admin GUI
would be cool too, as would having a servlet/JSP based admin client deployable
as a web archive.
If someone's looking for an interesting GUI project, Ap
Jason Godden writes:
> This is my first patch for PostgreSQL against the 7.5devel cvs (please advise if
> this is the wrong place to post patches). This patch simply enables the \xDD (or
> \XDD) hexadecimal import in the copy command (im starting with the simple stuff
> first). I did notice t
Dave Page wrote:
-Original Message-
From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
Don't get me wrong - pgadmin is cool - I especially recommend
it to my Windows oriented clients and colleagues who hate
using command lines.
Why not your Linux or FreeBSD oriented colleagues?
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: 05 November 2003 12:48
> To: PostgreSQL-development
> Subject: Re: [HACKERS] Open Sourcing pgManage
>
>
>
> "especially" != "only"
>
Very true :-)
> BTW, pgadmin could improve its Linux coverage somewha
This is my first patch for PostgreSQL against the 7.5devel cvs (please advise if this is the wrong place to post patches). This patch simply enables the \xDD (or \XDD) hexadecimal import in the copy command (im starting with the simple stuff first). I did notice that there may be a need to issue
Dave Page wrote:
Anyway, CommandPrompt have apparently done something cool and
they are
donating it and we should all be happy, no? :-)
With my PostgreSQL hat on, yes, it's a good thing. With my pgAdmin hat,
no, it's a bad thing!
I'm feeling quite relaxed about that. Competition stimulat
Alexey Mahotkin <[EMAIL PROTECTED]> writes:
> TL> upper/lower aren't going to work desirably in any multi-byte
> TL> character set encoding.
> Can you please point me at their implementation? I do not understand
> why that's impossible.
Because they use 's toupper() and tolower() funct
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> initdb: input file
> "/home/chriskl/pgsql/src/test/regress/./tmp_check/install//ho
> me/chriskl/local/share/postgresql/postgres.bki" does not belong to
> PostgreSQL 7.5devel
> I wiped the src/test dir, re cvs up'd and did gmake test again and
Jason Godden <[EMAIL PROTECTED]> writes:
> This is my first patch for PostgreSQL against the 7.5devel cvs (please
> advise if this is the wrong place to post patches).
pgsql-patches in future, please.
> +#define HEXVALUE(c) (((c)>='a') ? ((c)-87) : (((c)>='A') ? ((c)-55) : ((c)-'0')))
This seems
> > The only idea I have come up with is to move all buffer write operations
> > into a background writer process, which could easily keep track of
> > every file it's written into since the last checkpoint.
>
> I fear this approach. It seems to limit a lot of design flexibility later. But
> I
> My plan is to create another background process very similar to
> the checkpointer and to let that run forever basically looping over that
> BufferSync() with a bool telling that it's the bg_writer.
Why not use the checkpointer itself inbetween checkpoints ?
use a min and a max dirty setting l
Is this a bug we should fix for 7.3.5 when it eventually comes out?
On Tue, 4 Nov 2003, Andrew Rawnsley wrote:
>
> Just build RC1 today on Panther, no problems.
>
>
> On Nov 4, 2003, at 5:06 PM, Jeff Hoffmann wrote:
>
> > Tom Lane wrote:
> >> [EMAIL PROTECTED] writes:
> >>> After spending a f
On Tue, 4 Nov 2003, Gaetano Mendola wrote:
> I agree in general with you for these "general" arguments, but here we
> are talking about to introduce a sleep ( removable by guc ) or not! What
> about the hash refactoring introduced with 7.4? Are you going to
> discourage people to use the hash?
[EMAIL PROTECTED] (Greg Stark) writes:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
>
>> I think there is room for lots of GUIs, though, and having a Java
>> admin GUI would be cool too, as would having a servlet/JSP based
>> admin client deployable as a web archive.
>
> If someone's looking for an
I am trying to find information regarding creation of B-tree index in
postgres for variable length
character data (Char/varchar type). Specifically, what pagination policy
is used, does it use prefix,
or any other form of compression (encoding)?
Regards,
VJ Anand
---(
Zeugswetter Andreas SB SD wrote:
My plan is to create another background process very similar to
the checkpointer and to let that run forever basically looping over that
BufferSync() with a bool telling that it's the bg_writer.
Why not use the checkpointer itself inbetween checkpoints ?
use a mi
Christopher Browne <[EMAIL PROTECTED]> writes:
> Was that a 'native' part of SHELF? Or more related to their "TM1"
> product?
The full source was included in SHELF (if that was the source release I'm
thinking of.) I think it was called axdata.
> FYI, while Applix and VistaSource have "orphaned
The SuSE PPC guru said that the PPC spinlock code we currently use may
behave erroneously on multiprocessor systems. Attached is the proposed
patch, suggested for inclusion in 7.4. Comments?
--
Peter Eisentraut [EMAIL PROTECTED]
--- src/include/storage/s_lock.h
+++ src/include/storage/s_lock.
Here are some issues that might need to be addressed before 7.4 goes out:
* ECPG has some new include files such as
datetime.h
decimal.h
that come as part of the Informix compatibility mode. I don't think these
should be installed directly in $includedir because of potential
conflicts. We can'
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> The SuSE PPC guru said that the PPC spinlock code we currently use may
> behave erroneously on multiprocessor systems.
What's his evidence for that claim? The code we have is based directly
on the recommendations in the PPC manuals, and has been test
I've just uploaded
http://developer.postgresql.org/~wieck/all_performance.v4.74.diff.gz
This patch contains the "still not yet ready" performance improvements
discussed over the couple last days.
_Shared buffer replacement_:
The buffer replacement strategy is a slightly modified version of ARC
Since this is a large query, attachments for the explains / query.
Configuration:
dev_iqdb=# select version();
version
PostgreSQL 7.4beta1 on i386-portbld-freeb
Ð ÐÑÐ, 05.11.2003, Ð 16:25, Tom Lane ÐÐÑÐÑ:
> > +#define HEXVALUE(c) (((c)>='a') ? ((c)-87) : (((c)>='A') ? ((c)-55) : ((c)-'0')))
>
> This seems excessively dependent on the assumption that the character
> set is ASCII. Why have you hard-coded numeric equivalents into this
> macro?
What not AS
> > Why not use the checkpointer itself inbetween checkpoints ?
> > use a min and a max dirty setting like Informix. Start writing
> > when more than max are dirty stop when at min. This avoids writing
> > single pages (which is slow, since it cannot be grouped together
> > by the OS).
>
> Curren
Jan Wieck wrote:
_Vacuum page delay_:
Tom Lane's napping during vacuums with another tuning option. I
replaced the usleep() call with a PG_DELAY(msec) macro in miscadmin.h,
which does use select(2) instead. That should address the possible
portability problems.
What about skipping the delay if
Zeugswetter Andreas SB SD wrote:
> Why not use the checkpointer itself inbetween checkpoints ?
> use a min and a max dirty setting like Informix. Start writing
> when more than max are dirty stop when at min. This avoids writing
> single pages (which is slow, since it cannot be grouped together
> b
Jan Wieck <[EMAIL PROTECTED]> writes:
> This patch contains the "still not yet ready" performance improvements
> discussed over the couple last days.
Cool stuff!
> The buffer replacement strategy is a slightly modified version of
> ARC.
BTW Jan, I got your message about taking a look at the ARC
Manfred Spraul wrote:
Jan Wieck wrote:
_Vacuum page delay_:
Tom Lane's napping during vacuums with another tuning option. I
replaced the usleep() call with a PG_DELAY(msec) macro in miscadmin.h,
which does use select(2) instead. That should address the possible
portability problems.
What abou
Neil Conway wrote:
Jan Wieck <[EMAIL PROTECTED]> writes:
This patch contains the "still not yet ready" performance improvements
discussed over the couple last days.
Cool stuff!
The buffer replacement strategy is a slightly modified version of
ARC.
BTW Jan, I got your message about taking a look a
On Wed, 5 Nov 2003, Peter Eisentraut wrote:
> Here are some issues that might need to be addressed before 7.4 goes out:
>
> * ECPG has some new include files such as
>
> datetime.h
> decimal.h
>
> that come as part of the Informix compatibility mode. I don't think these
> should be installed di
Jan Wieck wrote:
How portable is getrusage()? Could the postmaster issue that
frequently for RUSAGE_CHILDREN and leave the result somewhere in the
shared memory for whoever is concerned?
SVr4, BSD4.3, SUS2 and POSIX1003.1, I believe.
I also believe there is a M$ dll available that gives that f
Hi All,
I work with Marc Fournier, for those who don't know, and have been
working extensively with the schemas feature for Hub.Org's new Account
Management package. Each client's data is stored in a seperate schema
set asside just for them (though they will never have direct access to
it, it he
On Thu, 6 Nov 2003 06:25 am, Markus Bertheau wrote:
> Ð ÐÑÐ, 05.11.2003, Ð 16:25, Tom Lane ÐÐÑÐÑ:
> > > +#define HEXVALUE(c) (((c)>='a') ? ((c)-87) : (((c)>='A') ? ((c)-55) :
> > > ((c)-'0')))
> >
> > This seems excessively dependent on the assumption that the character
> > set is ASCII. Why have
--On Thursday, November 06, 2003 07:43:07 +1100 Jason Godden
<[EMAIL PROTECTED]> wrote:
On Thu, 6 Nov 2003 06:25 am, Markus Bertheau wrote:
? ???, 05.11.2003, ? 16:25, Tom Lane ?:
> > +#define HEXVALUE(c) (((c)>='a') ? ((c)-87) : (((c)>='A') ? ((c)-55)
> > : ((c)-'0')))
>
> This seems exces
Andrew Dunstan wrote:
Jan Wieck wrote:
How portable is getrusage()? Could the postmaster issue that
frequently for RUSAGE_CHILDREN and leave the result somewhere in the
shared memory for whoever is concerned?
SVr4, BSD4.3, SUS2 and POSIX1003.1, I believe.
I also believe there is a M$ dll avai
On Wed, Nov 05, 2003 at 03:08:53PM -0500, Neil Conway wrote:
> Jan Wieck <[EMAIL PROTECTED]> writes:
> > I personally would like to see this work included in a 7.4.x
> > release.
>
> Personally, I can't see any circumstance under which I would view this
> as appropriate for integration into the 7.
Chris Bowlby wrote:
Hi All,
I work with Marc Fournier, for those who don't know, and have been
working extensively with the schemas feature for Hub.Org's new Account
Management package. Each client's data is stored in a seperate schema
set asside just for them (though they will never have direc
Jan Wieck <[EMAIL PROTECTED]> writes:
> Manfred Spraul wrote:
>> What about skipping the delay if there are no outstanding disk
>> operations?
> How portable is getrusage()? Could the postmaster issue that frequently
> for RUSAGE_CHILDREN and leave the result somewhere in the shared memory
> fo
On Wed, Nov 05, 2003 at 02:47:17PM -0600, Larry Rosenman wrote:
>
>
> --On Thursday, November 06, 2003 07:43:07 +1100 Jason Godden
> <[EMAIL PROTECTED]> wrote:
>
> >On Thu, 6 Nov 2003 06:25 am, Markus Bertheau wrote:
> >>? ???, 05.11.2003, ? 16:25, Tom Lane ?:
> >>> > +#define HEXVALUE(c) (
On Wed, Nov 05, 2003 at 03:49:54PM -0500, Jan Wieck wrote:
> Andrew Dunstan wrote:
>
> >Jan Wieck wrote:
> >
> >>
> >>How portable is getrusage()? Could the postmaster issue that
> >>frequently for RUSAGE_CHILDREN and leave the result somewhere in the
> >>shared memory for whoever is concerned?
On Wed, 5 Nov 2003, Jan Wieck wrote:
> Chris Bowlby wrote:
>
> > Hi All,
> >
> > I work with Marc Fournier, for those who don't know, and have been
> > working extensively with the schemas feature for Hub.Org's new Account
> > Management package. Each client's data is stored in a seperate schem
On Thu, 6 Nov 2003, Jason Godden wrote:
> On Thu, 6 Nov 2003 06:25 am, Markus Bertheau wrote:
> > Ð ÐÑÐ, 05.11.2003, Ð 16:25, Tom Lane ÐÐÑÐÑ:
> > > > +#define HEXVALUE(c) (((c)>='a') ? ((c)-87) : (((c)>='A') ? ((c)-55) :
> > > > ((c)-'0')))
> > >
> > > This seems excessively dependent on the assum
Jan Wieck <[EMAIL PROTECTED]> writes:
> As a matter of fact, people who have performance problems are likely to
> be the same who have upgrade problems. And as Gaetano pointed out
> correctly, we will see wildforms with one or the other feature applied.
I'd believe that for patches of the size o
Tom Lane wrote:
Manfred's idea is interesting but AFAICS completely unimplementable
in any portable fashion. You'd have to have hooks into the kernel.
I thought about outstanding operations from postgres - I don't know
enough about the buffer layer if it's possible to keep a counter of the
c
Chris Bowlby <[EMAIL PROTECTED]> writes:
> As you can see this is a nice, clean way to break down some datasets.
> But, if I do:
> set search_path to public, test_001, test_002;
> I only get access to the tables in test_001 and public, the tables in
> test_002 are not listed, and thus I do not
Stephan Szabo <[EMAIL PROTECTED]> writes:
> On Thu, 6 Nov 2003, Jason Godden wrote:
>> On Thu, 6 Nov 2003 06:25 am, Markus Bertheau wrote:
>>> +#define HEXVALUE(c) (((c)>='a') ? ((c)-87) : (((c)>='A') ? ((c)-55) :
> ((c)-'0')))
> I haven't looked at the code in question, but assuming the digits ar
Folks,
If possible, for the upcoming release we'd like to get the Contributor List on
developer.postgresql.org updated. Can everyone please take a gander at:
http://developer.postgresql.org/bios.php
... and tell me what's out of date other than me & Vadim? i.e.:
A) What contributors are mis
On Wed, 5 Nov 2003, Tom Lane wrote:
> Chris Bowlby <[EMAIL PROTECTED]> writes:
> > As you can see this is a nice, clean way to break down some datasets.
> > But, if I do:
>
> > set search_path to public, test_001, test_002;
>
> > I only get access to the tables in test_001 and public, the tab
Chris,
> I work with Marc Fournier, for those who don't know, and have been
> working extensively with the schemas feature for Hub.Org's new Account
> Management package. Each client's data is stored in a seperate schema
> set asside just for them (though they will never have direct access to
> i
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
>> How else would you expect it to work?
> List of relations
> Schema | Name | Type | Owner
> --+---+--+---
> public | categories| table| 18
Tom Lane wrote:
Jan Wieck <[EMAIL PROTECTED]> writes:
As a matter of fact, people who have performance problems are likely to
be the same who have upgrade problems. And as Gaetano pointed out
correctly, we will see wildforms with one or the other feature applied.
I'd believe that for pat
Josh Berkus <[EMAIL PROTECTED]> writes:
> B) What contributors are listed under Major Developers who haven't
> contributed any code since 7.1.0?
I think we had agreed that formerly-listed contributors would not be
deleted, but would be moved to a new section titled "Contributors
Emeritus" or some
Tom,
> I think we had agreed that formerly-listed contributors would not be
> deleted, but would be moved to a new section titled "Contributors
> Emeritus" or some such. Please make sure that Tom Lockhart and Vadim
> get listed that way, at least.
Yeah, I was thinking of moving them from "Major
Tom Lane wrote:
> Josh Berkus <[EMAIL PROTECTED]> writes:
> > B) What contributors are listed under Major Developers who haven't
> > contributed any code since 7.1.0?
>
> I think we had agreed that formerly-listed contributors would not be
> deleted, but would be moved to a new section titled "Con
Tom Lane wrote:
> Josh Berkus <[EMAIL PROTECTED]> writes:
> > B) What contributors are listed under Major Developers who haven't
> > contributed any code since 7.1.0?
>
> I think we had agreed that formerly-listed contributors would not be
> deleted, but would be moved to a new section titled "Con
Josh Berkus wrote:
Folks,
If possible, for the upcoming release we'd like to get the Contributor List on
developer.postgresql.org updated. Can everyone please take a gander at:
http://developer.postgresql.org/bios.php
... and tell me what's out of date other than me & Vadim? i.e.:
A) What
Guys,
Oh, and how about we kill the Image Map of major developers? It's about 4
years out of date, and makes developers.postgresql.org load like molasses in
January.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)--
Josh Berkus wrote:
> Guys,
>
> Oh, and how about we kill the Image Map of major developers? It's about 4
> years out of date, and makes developers.postgresql.org load like molasses in
> January.
Agreed. I think Jan is the only one who knows how to updated it. Jan?
--
Bruce Momjian
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Josh Berkus wrote:
>> Oh, and how about we kill the Image Map of major developers? It's about 4
>> years out of date, and makes developers.postgresql.org load like molasses in
>> January.
> Agreed.
Yeah. It was cute when we did it but it's overkill
Tom,
> Yeah. It was cute when we did it but it's overkill as a way of pointing
> out that we have a worldwide development community. We can just say
> that...
I'll be happy to re-do it someday using OOo's imagemapper. But not this week
...
--
-Josh Berkus
Aglio Database Solutions
San Fra
Josh Berkus <[EMAIL PROTECTED]> writes:
> Oh, and how about we kill the Image Map of major developers? It's about 4
> years out of date, and makes developers.postgresql.org load like molasses in
> January.
Personally, I don't really see the need for developer.postgresql.org
to be a separate su
On Wed, 5 Nov 2003, Rod Taylor wrote:
> Since this is a large query, attachments for the explains / query.
>
> Configuration:
> dev_iqdb=# select version();
> version
>
Josh Berkus writes:
> If possible, for the upcoming release we'd like to get the Contributor List on
> developer.postgresql.org updated. Can everyone please take a gander at:
> http://developer.postgresql.org/bios.php
One thing that really puzzles me is this web page:
http://advocacy.postgresq
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> The SuSE PPC guru said that the PPC spinlock code we currently use may
> behave erroneously on multiprocessor systems. Attached is the proposed
> patch, suggested for inclusion in 7.4. Comments?
I looked into this some more. The current CVS tip is
Neil Conway writes:
> Personally, I don't really see the need for developer.postgresql.org
> to be a separate sub-site. Since it is basically just a collection of
> links to other resources (CVSweb, TODO list, devel docs build, etc.),
> why not just make it a page or two on www.postgresql.org?
I
Bruce Momjian wrote:
Tom Lane wrote:
Josh Berkus <[EMAIL PROTECTED]> writes:
B) What contributors are listed under Major Developers who haven't
contributed any code since 7.1.0?
I think we had agreed that formerly-listed contributors would not be
deleted, but would be moved to a n
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> * Fix uselessly executable files in the source tree. See my recent post.
> Any ideas on that?
They've been uselessly executable since they were put there. I don't
think this is something that we need to fix in time for 7.4, or even
should risk tryin
> I'm not sure if that will actually change the default_statistics_target of
> the tables you're analyzing, I think it will only apply to newly created
> tables.
>
> I believe you have to alter table alter column set statistics 1000 for
> each column you want a statistic of 1000. You might w
Rod Taylor <[EMAIL PROTECTED]> writes:
>> I'm not sure if that will actually change the default_statistics_target
> Hmm.. I was under the impression that it would work for any tables that
> haven't otherwise been overridden.
It will. I think Scott is recalling the original circa-7.2
implementati
On Wed, 2003-11-05 at 18:57, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> >> I'm not sure if that will actually change the default_statistics_target
>
> > Hmm.. I was under the impression that it would work for any tables that
> > haven't otherwise been overridden.
>
> It will. I t
Rod Taylor <[EMAIL PROTECTED]> writes:
> Effectively, the planner has amazingly inaccurate row estimates.
It seems the key estimation failure is in this join step:
-> Hash Join (cost=1230.79..60581.82 rows=158 width=54) (actual
time=1262.35..151200.29 rows=1121988 loops=1)
On Wed, 5 Nov 2003, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> >> I'm not sure if that will actually change the default_statistics_target
>
> > Hmm.. I was under the impression that it would work for any tables that
> > haven't otherwise been overridden.
>
> It will. I think Sco
On Wed, 2003-11-05 at 19:18, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > Effectively, the planner has amazingly inaccurate row estimates.
>
> It seems the key estimation failure is in this join step:
>
> -> Hash Join (cost=1230.79..60581.82 rows=158 width=54) (actual
Peter,
> http://advocacy.postgresql.org/about/
>
> This is sort of the same web page that we're talking about here, but it
> lists the developers below the press contacts as also-rans. What's worse,
> this is the web page that people will get to if they go to if they go to
> http://www.postgres
Actually, the use of schema's was my idea, to speed up some dreadfully
slow queries dealing with traffic stats from a table that was growing
painfully monolithic ... the idea is/was that it would be easier to
backup/remove all data pertaining to a specific client if they decided to
close their acc
* Fix uselessly executable files in the source tree. See my recent post.
Any ideas on that?
As far as I'm aware, the only way to fix this is to get into the cvsroot
and chmod them by hand.
Chris
---(end of broadcast)---
TIP 5: Have you checked
Josh Berkus wrote:
Folks,
If possible, for the upcoming release we'd like to get the Contributor List on
developer.postgresql.org updated. Can everyone please take a gander at:
http://developer.postgresql.org/bios.php
... and tell me what's out of date other than me & Vadim? i.e.:
A) What
I think we had agreed that formerly-listed contributors would not be
deleted, but would be moved to a new section titled "Contributors
Emeritus" or some such. Please make sure that Tom Lockhart and Vadim
get listed that way, at least.
I think the "Emeritus" word might be too hard for non-native En
I think the "Emeritus" word might be too hard for non-native English
speakers, and even for less educated English speakers.
Isn't that an even better reason to use it? :)
My personal opinion would be that they can use dictionary.com if they
don't know what it means.
Chris
---
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Actually, the use of schema's was my idea, to speed up some dreadfully
> slow queries dealing with traffic stats from a table that was growing
> painfully monolithic ... the idea is/was that it would be easier to
> backup/remove all data pertaining
> #define HEXVALUE(c) \
> (((c) >= '0' && (c) <= '9') ? ((c) - '0') : \
>(((c) >= 'A' && (c) <= 'F') ? ((c) - 'A' + 10) : \
> ((c) - 'a' + 10)))
>
> 3. The third level would be to get rid of the assumption that letters
> are contiguous, which would probably require making a lo
85 matches
Mail list logo
