Dear Tatsuo,
Thanks for your reply, as I noticed from the source code that your name
often appears when dealing with multi-byte issues;-)
On Fri, 12 Mar 2004, Tatsuo Ishii wrote:
As far as I understand your code, it will be broken on many multi byte
encodings.
1) a character is not always
-Original Message-
From: Josh Berkus [mailto:[EMAIL PROTECTED]
Sent: 11 March 2004 23:14
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [pgsql-www] The Name Game: postgresql.net vs. pgfoundry.org
B) Favor www.pgfoundry.org
I don't really mind too much either way, but if
Fabien COELHO wrote:
There is also a localisation issue here, as the translation of both
lines must match so that the alignment is kept. I thought that if it
is the very same word, the translation should be the same.
You can just indent with as many spaces. This is done in other places
Michael Glaesemann wrote:
Just to speak up (as an avid lurker), I agree with Jeroen that this
distinction is quite subtle and may cause confusion. Some may even
expect the two to resolve to the same site, as a lot of popular sites
own .com/.net/.org, all resolving to the same site.
Speaking of
Josh Berkus
But possible more error prone. If you crank up the default
statistics
to
50, but the index default is still 25... OTOH, you could always
have
the
setting of used for index default be whichever is greater... hmmm.
Well, I'm not 100% opposed to a multiplier. I'd like to
Hannu Krosing
Josh Berkus kirjutas T, 09.03.2004 kell 19:46:
In my personal experience, the *primary* use of PITR is recovery
from
User
Error. For example, with one SQL Server 7.0 installation for a law
firm,
I've made use of PITR 4 times over the last 4 years: once was
because
and HDD
Dear Tatsuo,
Thanks for your reply, as I noticed from the source code that your name
often appears when dealing with multi-byte issues;-)
On Fri, 12 Mar 2004, Tatsuo Ishii wrote:
As far as I understand your code, it will be broken on many multi byte
encodings.
1) a character is not
On Wed, Mar 10, 2004 at 11:43:48AM -0500, Bruce Momjian wrote:
The problem with gprof is that I am going to see all the backend startup
stuff too, no? Is there a way to get a dump just the run of the query?
I was sort of lurking on this thread, waiting to see what became of it. Did
nobody
Hello,
I'm watching a strange beahviour by postgres,
I wonder if it's a memory leak:
Creating an index and destroying it makes the
postgres process grow in size. This is what I do:
create table test (a int);
create index test_idx on test (a); drop index test_idx;
create index test_idx on test
However, some of the porting team felt that it would be
confusing for people
who typed in www.postgresql.net to be presented with the
GForge interface,
and suggested that we use the domain after what we'll be
calling the new
Tool, namely pgFoundry, thus putting stuff at
PQmblen returns the storage size, which is not necessarily same as the
character width reprensented in a terminal. For example for a kanji
character in UTF-8 PQmblen returns 3, but it ocuppies 2 x ASCII
character space, not x 3. Isn't that a problem for you?
2) It assume all encodings are
Dear Tatsuo,
1) a character is not always represented on a terminal propotional to
the storage size. For example a kanji character in UTF-8 encoding
has a storage size of 3 bytes while it occupies spaces only twice
of ASCII characters on a terminal. Same thing can be said to
PQmblen returns the storage size, which is not necessarily same as the
character width reprensented in a terminal. For example for a kanji
character in UTF-8 PQmblen returns 3, but it ocuppies 2 x ASCII
character space, not x 3. Isn't that a problem for you?
If I read you correctly, you
Josh Berkus wrote:
Folks,
As we discussed a couple weeks ago, Marc, Andrew, Tim Perdue, Chris Ryan and I
are testing implementing GForge in place of GBorg for associated projects for
PostgreSQL.
One thing which was suggested initially was that this new project hosting site
be at
Tom Lane wrote:
Fernando Nasser [EMAIL PROTECTED] writes:
Please remind me again why the postmaster cannot close and open the log
file when it receives a SIGHUP (to re-read configuration)?
(a) Because it never opened it in the first place --- the log file is
whatever was passed as stderr.
(b)
Fabien COELHO [EMAIL PROTECTED] writes:
As a compromise, I can suggest the following:
LINE 4: WHERE id=123 AND name LIKE 'calvin' GROP BY name...
^
That works for me. I don't mind it saying LINE 1: in the one-line case.
It's not going to add more
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]
Sent: 12 March 2004 13:57
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [HACKERS] The Name Game: postgresql.net vs. pgfoundry.org
Isn't gforge a pgsql related project itself?
So I'd suggest:
Dear Tatsuo,
One thing I have to note is that some Asian characters such as Japanese,
Chinese require twice the space on a terminal for each character
comparing with plain ASCII characters. This is hard to explain to those
who are not familiar with kanji...
I learnt a little bit of chinese
On Fri, Mar 12, 2004 at 02:42:47PM -, Dave Page wrote:
We need some distinction between the core project sites and other
project sites - istm that a different domain is the only way to do that.
Okay, then how about postgres-extra.net, or forpostgres.net?
Saying Postgres instead of
strk [EMAIL PROTECTED] writes:
The size growth is reported by 'top' in the fields
SIZE, RSS and SHARE.
Can it be a memory leak in postgres code ?
No, you are misinterpreting the 'top' output.
You didn't say what platform you are on, but on some systems 'top'
increases the reported size of a
Dave Page wrote:
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]]
Sent: 12 March 2004 13:57
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [HACKERS] The Name Game: postgresql.net vs. pgfoundry.org
Isn't gforge a pgsql related project
[ I'm pushing Robert's comment over into the pghackers thread... ]
Robert Treat [EMAIL PROTECTED] writes:
I wasn't going to force the issue just for my own sake... but ISTM Tom, Peter,
myself and possibly others were all confused somewhat by the switch.
Anyway... the only real point that I
Could you take a look at included screen shot?
I haven't found it. However I've made a little bit of trying with my
Oops. I have included this time.
Maybe you could point me some source of information about display lengths
of characters depending on the encoding?
I could write
On Sat, 13 Mar 2004, Tatsuo Ishii wrote:
Oops. I have included this time.
How ! a japanese vi !
I could write PQmbtermlen function for every encoding supported by
PostgreSQL
That would be great ! ;-)
Ok, I will work on this.
Thanks.
--
Fabien Coelho - [EMAIL PROTECTED]
Jeroen T. Vermeulen [EMAIL PROTECTED] writes:
On Fri, Mar 12, 2004 at 02:42:47PM -, Dave Page wrote:
We need some distinction between the core project sites and other
project sites - istm that a different domain is the only way to do that.
Okay, then how about postgres-extra.net, or
On Fri, 2004-03-12 at 10:37, Tom Lane wrote:
Jeroen T. Vermeulen [EMAIL PROTECTED] writes:
On Fri, Mar 12, 2004 at 02:42:47PM -, Dave Page wrote:
We need some distinction between the core project sites and other
project sites - istm that a different domain is the only way to do that.
On Fri, Mar 12, 2004 at 10:37:58AM -0500, Tom Lane wrote:
Well, if you want to think along those lines, I believe that we (PGDG)
currently hold these domain names:
[...]
postgres.org
This is the one I was silently rooting for, but figured was too good to
be true.
You could make a
On Fri, 2004-03-12 at 10:14, Andrew Dunstan wrote:
Dave Page wrote:
-Original Message-
From: Andreas Pflug [ mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] ]
Sent: 12 March 2004 13:57
To: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] mailto:[EMAIL
Hi,
I know that we have more and more details to show, during vacuum analyze ...
but since v7.4.x it's not really easy to read quicly a vacuum analyze to see
important points ... like elapsed time or number of tupples deleted...
I would like to know first if you could make an effort about this
[EMAIL PROTECTED] writes:
- Re uni-directional logs
Of course. I forgot about PG's non-in-place update mechanisms and the
use of VACCUUM .. with versioning there are really no undo logging
necessary. I guess that means that during VACCUUM you might have to
significant work in indexes ? I'm
quote who=Tom Lane
My feeling is that we want people to consider these projects as closely
tied to the Postgres community and so postgresql.something is just right.
I can see there are different opinions out there though...
foundry.postgresql.org?
---(end of
On Fri, Mar 12, 2004 at 10:43:34AM -0600, Thomas Swan wrote:
foundry.postgresql.org?
Been through that one... Too long when you have to add project name as
well.
Jeroen
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Tuesday 09 March 2004 17:38, Simon Riggs wrote:
Richard Huxton
On Monday 08 March 2004 23:28, Simon Riggs wrote:
PITR Functional Design v2 for 7.5
Review of current Crash Recovery
Is there any value in putting this section on techdocs or similar? We
do
get a
small but
On Thu, 11 Mar 2004, Joshua D. Drake wrote:
IMHO, the domain name isn't the make/break of whether going to GForge will
succeed ... the success will be a matter of marketing it, and making sure
that its project are well known ... personally, focusing on the domain is
like focusing on the
Robert,
maybe pgsqlfoundry is a better compromise?
No, too long.People'd end up calling it pgFoundry anyway.
Besides, Gavin Roy already designed us a nice pgFoundry logo. ;-)
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of
On Fri, 2004-03-12 at 11:52, Jeroen T. Vermeulen wrote:
On Fri, Mar 12, 2004 at 10:43:34AM -0600, Thomas Swan wrote:
foundry.postgresql.org?
Been through that one... Too long when you have to add project name as
well.
I don't understand why. Presumably the postgresql.org website will
Fernando,
I don't really care on how its done, but IMO an enterprise class
database must be able to do log rotation. Logging to Syslog is not an
option (specially with our verbosity) -- users must be able to use flat
files for logging.
Hmmm ... to differ: I have several (six, actually)
Tom Lane wrote:
Well, if you want to think along those lines, I believe that we (PGDG)
currently hold these domain names:
postgresql.org
postgresql.com
postgresql.net
postgres.org
postgres.com
It looks like some domain squatter has his tentacles on
David Garamond [EMAIL PROTECTED] writes:
Also, we're targetting the developers right? Please do not consider
ourselves as being too stupid to differentiate between postgresql.org and
postgresql.net...
I can never remember whether the current site is postgresql.{com,org,net} even
now. Making
Joe,
Looks like he hasn't been squatting all that long:
Domain Name: POSTGRES.NET
Created on..: Wed, Aug 07, 2002
Expires on..: Sat, Aug 07, 2004
Record last updated on..: Fri, Oct 31, 2003
Also note the expiration date. Maybe we can
Josh Berkus wrote:
Looks like he hasn't been squatting all that long:
Domain Name: POSTGRES.NET
Created on..: Wed, Aug 07, 2002
Expires on..: Sat, Aug 07, 2004
Record last updated on..: Fri, Oct 31, 2003
Also note the expiration date. Maybe we can
On Fri, Mar 12, 2004 at 09:24:28 -0500,
Fernando Nasser [EMAIL PROTECTED] wrote:
I don't really care on how its done, but IMO an enterprise class
database must be able to do log rotation. Logging to Syslog is not an
option (specially with our verbosity) -- users must be able to use flat
Bruno Wolff III [EMAIL PROTECTED] writes:
Are you suggesting the that postgres project develop their own logger
rather than people just using one that has already been developed
by some other group?
The problem from the point of view of Red Hat is to not introduce a
dependency from the
The problem with gprof is that I am going to see all the backend
startup
stuff too, no? Is there a way to get a dump just the run of the
query?
I was sort of lurking on this thread, waiting to see what became of
it.
Did
nobody actually come to a conclusion on what that last msec was
On Fri, Mar 12, 2004 at 13:17:50 -0500,
Tom Lane [EMAIL PROTECTED] wrote:
Bruno Wolff III [EMAIL PROTECTED] writes:
Are you suggesting the that postgres project develop their own logger
rather than people just using one that has already been developed
by some other group?
The problem
On Fri, 12 Mar 2004, Tom Lane wrote:
This also brings up the thought that if we do want to use pgfoundry.org,
we'd better register pgfoundry.net and pgfoundry.com before someone else
does.
I did all three simultaneously for exactly that reason
Marc G. Fournier Hub.Org
On Fri, 12 Mar 2004, Rod Taylor wrote:
On Fri, 2004-03-12 at 13:30, Marc G. Fournier wrote:
On Fri, 12 Mar 2004, Rod Taylor wrote:
Having all PostgreSQL related material under one domain is beneficial to
the project. Our big issue isn't the domain is too long, it is difficult
find
On Fri, 2004-03-12 at 13:30, Marc G. Fournier wrote:
On Fri, 12 Mar 2004, Rod Taylor wrote:
Having all PostgreSQL related material under one domain is beneficial to
the project. Our big issue isn't the domain is too long, it is difficult
find the subproject in the first place.
the
Marc G. Fournier [EMAIL PROTECTED] writes:
the projects site will not be under postgresql.org ... postgresql.net is
available for it, but not postgresql.org ... we are keeping that domain
clean for any future stuff we want to do with the core project ...
I agree we don't want
On Fri, 12 Mar 2004, Greg Stark wrote:
I would say follow the same model as modules.apache.org, pear.php.net,
etc.
note that having projects.postgresql.org is cool ... its just the projects
subpages that I'm objecting too ...
the easiest is to have http://projects.postgresql.org point to the
On Fri, 12 Mar 2004 13:36:47 -0500
Tom Lane [EMAIL PROTECTED] wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
the projects site will not be under postgresql.org ...
postgresql.net is available for it, but not postgresql.org ... we
are keeping that domainclean for any future stuff we want
On Fri, 12 Mar 2004, Tom Lane wrote:
Since we do already own pgfoundry.org, could we satisfy everybody by
dual-naming the project sites? That is, have both
project.pgfoundry.org
project.pgfoundry.postgresql.org
point to the same place?
no objection here ... my only object
Tom,
Since we do already own pgfoundry.org, could we satisfy everybody by
dual-naming the project sites? That is, have both
project.pgfoundry.org
project.pgfoundry.postgresql.org
point to the same place?
Sounds good to me if it's doable via DNS.
--
-Josh Berkus
Aglio
On Fri, 12 Mar 2004, Josh Berkus wrote:
Tom,
Since we do already own pgfoundry.org, could we satisfy everybody by
dual-naming the project sites? That is, have both
project.pgfoundry.org
project.pgfoundry.postgresql.org
point to the same place?
Sounds good to me if it's
On Friday 12 March 2004 09:24 am, Fernando Nasser wrote:
I don't really care on how its done, but IMO an enterprise class
database must be able to do log rotation. Logging to Syslog is not an
option (specially with our verbosity) -- users must be able to use flat
files for logging.
Uh, we
On Fri, 2004-03-12 at 13:36, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
the projects site will not be under postgresql.org ... postgresql.net is
available for it, but not postgresql.org ... we are keeping that domain
clean for any future stuff we want to do with the core
Bruno Wolff III wrote:
I can see their problem with making a dependency to all of apache or including
multilog in their distribution. But they probably could include something
that is only a logger either using some project that is only a logger or
splitting out the logger that is bundled with
Bruce Momjian wrote:
What killed the idea of doing ssl or kerberos locking inside libpq was
that there was no way to be sure that outside code didn't also access
those routines.
A callback based implementation can handle that: libpq has a default
implementation for apps that do not use openssl
Hi Lamar,
Lamar Owen wrote:
On Friday 12 March 2004 09:24 am, Fernando Nasser wrote:
I don't really care on how its done, but IMO an enterprise class
database must be able to do log rotation. Logging to Syslog is not an
option (specially with our verbosity) -- users must be able to use flat
On Fri, Mar 12, 2004 at 15:19:29 -0500,
Fernando Nasser [EMAIL PROTECTED] wrote:
Bruno Wolff III wrote:
I can see their problem with making a dependency to all of apache or
including
multilog in their distribution. But they probably could include something
that is only a logger either
I've been looking into Paolo Tavalazzi's recent report of discrepancies
in the planner's estimates and resulting plan choices when the order of
FROM-clause entries is changed. Here is a boiled-down example:
paolo=# explain select * from seat, spettacoli, tran
paolo-# where tran.id = 42 and
I've been toying with the notion of allowing the planner to compute the
current values of stable functions when it's trying to estimate
selectivities. For instance, in a query like
select ... where timestampcol = now() - interval '1 day';
we currently throw up our hands and treat the
Rod Taylor [EMAIL PROTECTED] writes:
It would not be correct to reduce the righthand side to a constant in
advance of execution, of course, but is it reasonable to compute its
current value solely for purposes of comparison to column statistics?
So this means it would be double evaluated? A
Andrew Dunstan [EMAIL PROTECTED] writes:
Did anything ever come from this thread?
http://archives.postgresql.org/pgsql-hackers/2003-05/msg00603.php
(Heading: Plan B for log rotation support: borrow Apache code)
Only an entry on my depressingly long personal to-do list :-(
I did take a look
On Fri, Mar 12, 2004 at 01:02:00PM -0600, Frank Wiles wrote:
As for the length of the URL, I think any developer or user
of PostgreSQL is knowledgeable enough to take advantage of browser
bookmarks. :)
I've heard this said a several times now, but that doesn't make me feel
any
65 matches
Mail list logo
