On Wed, 2005-05-04 at 10:56 +1000, Neil Conway wrote:
Dag-Erling Smrgrav wrote:
It doesn't stress the system anywhere near enough to reveal bugs in,
say, the shared memory or semaphore code.
I agree -- I think we definitely need more tests for the concurrent
behavior of the system.
Any chance one of you fine people could start another thread?
This has very little to do with Feature freeze date for 8.1...
Thanks,
Best Regards, Simon Riggs
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Neil Conway [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav wrote:
It doesn't stress the system anywhere near enough to reveal bugs in,
say, the shared memory or semaphore code.
I agree -- I think we definitely need more tests for the concurrent
behavior of the system.
Quite, but in the
Quite, but in the meantime, a good benchmark should stress the system
enough to cause crashes, lockups or at least incorrect results if a
bug is introduced in the shared memory or semaphore code, and will
definitely reveal any slowdowns introduced by new code, so my question
is: where can I find a
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Marc
G. Fournier
Sent: 03 May 2005 19:09
To: Joshua D. Drake
Cc: Marc G. Fournier; Tom Lane; Peter Eisentraut; Bruce
Momjian; PostgreSQL-development
Subject: Re: [pgsql-advocacy] [HACKERS]
On Wed, 4 May 2005 04:40 am, Tom Copeland wrote:
On Tue, 2005-05-03 at 14:26 -0400, Mitch Pirtle wrote:
If you guys are planning on running Gforge, then you better make 'box'
plural.
I'm running MamboForge.net, and the poor thing is getting beat into
the cold hard earth every day. We
This has very little to do with Feature freeze date for 8.1...
And btw I lost track of the thread. was any actual feature freeze date for 8.1
approved?
---(end of broadcast)---
TIP 6: Have you searched our list archives?
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
As for CVS - if we can't do development the way we want using it then it's
time to replace it.
CVS's capabilities (or lack of same) are completely unrelated to the
matter in hand. What we are talking about is packaging, ie what
2) As long as we're using CVS, the only way to
organize autonomous project
teams that have authority over their special areas
but no ability to change
central code is to push out projects to separate
CVS trees.
This has never been an issue before, AFAIK, nobody
with commit
Rob Butler wrote:
[details of some SVN features]
please see reecent debates on the topic of SCM systems.
Those who do not remember the debates on the mailing lists are bound to
repeat them.
cheers
andrew
---(end of broadcast)---
TIP 2: you can
Rob Butler wrote:
... SVN also has a number of nice features
like atomic commits, versioning directories, etc.
Still, subversion identifies file content by it's location in the
directory tree which makes the directory versioning a lot less useful
than it could have been. Renaming directories or
The world rejoiced as [EMAIL PROTECTED] (Andrew Dunstan) wrote:
As for CVS - if we can't do development the way we want using it
then it's time to replace it. I have been convinced for quite a
while that it is living on borrowed time, but I am far less certain
about what should be used to
Centuries ago, Nostradamus foresaw when josh@agliodbs.com (Josh Berkus) would
write:
Look at other large projects with lots of options. Apache, Perl, Linux,
Java,
emacs, KDE, etc., all of them strike a balance between including stuff and
leaving stuff as add-ins (some more narrowly than
Josh Berkus wrote:
Mischa,
Okay, although given the track record of page-based sampling for
n-distinct, it's a bit like looking for your keys under the streetlight,
rather than in the alley where you dropped them :-)
Bad analogy, but funny.
The issue with page-based vs. pure random sampling is
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Quite, but in the meantime, a good benchmark should stress the system
enough to cause crashes, lockups or at least incorrect results if a
bug is introduced in the shared memory or semaphore code, and will
definitely reveal any slowdowns
Kaare Rasmussen [EMAIL PROTECTED] writes:
This has very little to do with Feature freeze date for 8.1...
And btw I lost track of the thread. was any actual feature freeze date
for 8.1 approved?
July 1 is the plan ... subject to change of course ...
regards, tom lane
Tom wrote:
Don't worry, I'll veto any immediate removal of functionality ;-)
The correct way to handle this is to add some better userlock
functionality and deprecate what's there. We can remove the crufty
stuff in a release or three after it's been officially deprecated
... but there is no
Tom Lane wrote:
And btw I lost track of the thread. was any actual feature freeze date
for 8.1 approved?
July 1 is the plan ... subject to change of course ...
Incidentally, the way this was discussed/announced has been just right,
IMHO. Big improvement over last year.
cheers
andrew
OK, so the real issue is how do we make pgfoundry work.
My issue is that by pushing all collateral projects off to another site
makes it difficult for people
who are not familiar with the project to find what they are looking for
or even to know what there is to look for.
I'm sure there are
On Wed, 4 May 2005, Christopher Browne wrote:
A fairer comparison would be the BSD core systems. I believe that most
of them have a considerably larger set of stuff in the central CVS...
Yup, and *everyone* with commit accesss has access to *everything* ... I
could intruduce a 1 bit change to
Yup, and *everyone* with commit accesss has access to *everything* ... I
could intruduce a 1 bit change to one of the kernel sources and there is
a chance that nobody would ever notice it ... and this includes (or, at
least, the last time I did any work) port committers ...
Using cvsacls could
On Wed, 4 May 2005, Dave Cramer wrote:
OK, so the real issue is how do we make pgfoundry work.
My issue is that by pushing all collateral projects off to another site makes
it difficult for people
who are not familiar with the project to find what they are looking for or
even to know what there
On Wed, 4 May 2005, Andrew Dunstan wrote:
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
As for CVS - if we can't do development the way we want using it then it's
time to replace it.
CVS's capabilities (or lack of same) are completely unrelated to the
matter in hand. What we are
On Wed, 4 May 2005, Alvaro Herrera wrote:
On Tue, May 03, 2005 at 09:19:41PM -0700, Josh Berkus wrote:
I do find it kind of funny that we include the PLs but not the server-side
drivers, but that decision precedes my tenure on Core.
Sorry, you lost me -- what are server-side drivers?
Oh, good ...
On Wed, 4 May 2005, Dave Cramer wrote:
2) As long as we're using CVS, the only way to organize autonomous project
teams that have authority over their special areas but no ability to change
central code is to push out projects to separate CVS trees.
This has never been an issue before, AFAIK,
On Wed, 4 May 2005, Christopher Kings-Lynne wrote:
Yup, and *everyone* with commit accesss has access to *everything* ... I
could intruduce a 1 bit change to one of the kernel sources and there is a
chance that nobody would ever notice it ... and this includes (or, at
least, the last time I did
Marc G. Fournier wrote:
Just curious here ... but do any of the version control systems
provide per directory user restrictions? Where I could give CVS
access to Joshua, for instance, just to the plphp directory?
Serious question here, since I don't know, I only know CVS can't (or,
rather,
On Wednesday 04 May 2005 8:18 pm, Marc G. Fournier wrote:
Just curious here ... but do any of the version control systems provide
per directory user restrictions? Where I could give CVS access to
Joshua, for instance, just to the plphp directory?
Subversion does.
On Wed, 4 May 2005, Marc G. Fournier wrote:
Just curious here ... but do any of the version control systems provide
per directory user restrictions? Where I could give CVS access to
Joshua, for instance, just to the plphp directory?
Just how many incidents where people change the wrong
Dennis Bjorklund wrote:
On Wed, 4 May 2005, Marc G. Fournier wrote:
Just curious here ... but do any of the version control systems provide
per directory user restrictions? Where I could give CVS access to
Joshua, for instance, just to the plphp directory?
Just how many incidents where people
On Mon, 2 May 2005, Alvaro Herrera wrote:
The 2PC patch by Heikki Linnakangas (sp?) is also waiting and so far I
haven't seen any indication that it may be merged.
Actually, its one of the features we have planned to have merged for 8.1
... :)
Marc G. Fournier Hub.Org Networking
On Wednesday 04 May 2005 03:20, Christopher Kings-Lynne wrote:
Quite, but in the meantime, a good benchmark should stress the system
enough to cause crashes, lockups or at least incorrect results if a
bug is introduced in the shared memory or semaphore code, and will
definitely reveal any
On Wed, 4 May 2005, Joshua D. Drake wrote:
Just how many incidents where people change the wrong files do you except.
Maybe it's just easier to handle one such case every third year than to
set up some system to prevent it.
The number of incidents isn't the issue, the fact that it
Folks,
Sorry, you lost me -- what are server-side drivers?
Oh, good ... I ended up sending Josh an email offlist asking this, cause I
figured I was missing something ... but now I feel vindicated(?) knowing
I'm not the only one confused by this one :)
Drivers that get used on the server at
On Wed, 4 May 2005, Josh Berkus wrote:
Folks,
Sorry, you lost me -- what are server-side drivers?
Oh, good ... I ended up sending Josh an email offlist asking this, cause I
figured I was missing something ... but now I feel vindicated(?) knowing
I'm not the only one confused by this one :)
Drivers
Marc G. Fournier wrote:
On Wed, 4 May 2005, Josh Berkus wrote:
Folks,
Sorry, you lost me -- what are server-side drivers?
Oh, good ... I ended up sending Josh an email offlist asking this,
cause I
figured I was missing something ... but now I feel vindicated(?) knowing
I'm not the only one
On Wed, 4 May 2005, Joshua D. Drake wrote:
Marc G. Fournier wrote:
On Wed, 4 May 2005, Josh Berkus wrote:
Folks,
Sorry, you lost me -- what are server-side drivers?
Oh, good ... I ended up sending Josh an email offlist asking this, cause
I
figured I was missing something ... but now I feel
It's entirely likely that we haven't figured out how to make pgfoundry
work yet. But figure it out we must, or the project-as-a-whole will die
of its own weight. Not everything can be part of the core.
PgFoundry is coming along in its own right. I see three main problems
with it at current:
Joshua D. Drake wrote:
PgFoundry is coming along in its own right. I see three main problems
with it at current:
1. It looks like a separate project from PostgreSQL (website, name,
etc...)
I've been working on porting the site to use a derived theme from the
main PostgreSQL site. My main
Yes. Something simple that can provide clear, tangible benefits is the
best kind of improvement.
I am sure that adding parameters to the command line of PostgreSQL which
enables superior tuning for differing computer systems would be wildly
appreciated.
-Original Message-
From: [EMAIL
On Monday 02 May 2005 15:12, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
On Mon, 2 May 2005, Bruce Momjian wrote:
Marc G. Fournier wrote:
Then what is the point of having it in CVS? Other then to make are tar
ball bigger?
So it can be maintained with other PL languages
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 04, 2005 12:44 PM
To: Dann Corbit
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: Priority Mechanisms for OLTP and Transactional Web
Applications
Dear
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 04, 2005 12:44 PM
To: Dann Corbit
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: Priority Mechanisms for OLTP and Transactional Web
Applications
[ catching up... ]
James William Pye [EMAIL PROTECTED] writes:
I asked on IRC and I'm still curious, does PG have a API styling
standard/guide? I see formatting and info about error messages, but
nothing about function/global/typedef naming.
Nothing official, but here's a few random thoughts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to run a Perl script connecting to a PostgreSQL database via
DBI and DBD::Pg as a cron job. I'm already using the .pgpass mechanism
for managing md5 passwords on the client side and would like to use the
same mechanism for connecting
Andrew Dunstan wrote:
Tom Lane wrote:
And btw I lost track of the thread. was any actual feature freeze date
for 8.1 approved?
July 1 is the plan ... subject to change of course ...
Incidentally, the way this was discussed/announced has been just right,
IMHO. Big
Dave Held wrote:
developers and users of PostgreSQL. Everyone is welcome to
subscribe and take part in the discussions. (See the
a href=http://www.postgresql.org/docs/faqs.FAQ_DEV.html;
Developer's FAQ/A for information on how to get
involved in PostgreSQL
Using cvsacls could deal with that particular problem. Take the PHP
project's 1500 committers, and how they can only modify particular files.
cvsacls? got a URL for that that I can read?
http://sourceforge.net/docman/display_doc.php?docid=772group_id=1#top
Chris
---(end
Hi Evgen,
I just keep pinging this patch thread every once in a while to make sure
it doesn't get forgotten :)
How is the syncing with 8.1 CVS coming along?
Chris
Evgen Potemkin wrote:
Hi hackers!
I have done initial implementation of SQL99 WITH clause (attached).
It's now only for v7.3.4 and
Rosser Schwarz wrote:
while you weren't looking, Bruce Momjian wrote:
Adjustments?
A couple slight tweaks and rephrasings:
pIf you're looking for a PostgreSQL gatekeeper, central committe or
controlling company, give up; there isn't one. We do have a core
committe and don't hand out
Peter Eisentraut wrote:
Am Montag, 2. Mai 2005 20:14 schrieb Bruce Momjian:
I posted this compromise and no one replied so I thought everyone was OK
with it. It gets it into CVS, but has a separate compile stage to deal
with the recursive dependency problem.
How will a separate compile
Bruce Momjian pgman@candle.pha.pa.us writes:
My idea is that the second stage would just have them go to src/pl/plphp
and type 'gmake install'.
Absolutely not. It has to work as an independent package, not as
something that expects to build inside an already-configured Postgres
source tree.
Tom Lane wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
My idea is that the second stage would just have them go to src/pl/plphp
and type 'gmake install'.
Absolutely not. It has to work as an independent package, not as
something that expects to build inside an already-configured Postgres
Why actual rows=0?
I couldn't think of any reasonably cheap way to count the actual rows
(especially in the presence of lossy bitmaps), so I just punted.
I see.
BTW is it possible to let BitmapHeapScan fetch tuples by TID order? It
would make heap acccess in sequential manner and would
On Wed, 4 May 2005, Joshua D. Drake wrote:
Tom Lane wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
My idea is that the second stage would just have them go to src/pl/plphp
and type 'gmake install'.
Absolutely not. It has to work as an independent package, not as
something that expects to
Tatsuo Ishii [EMAIL PROTECTED] writes:
BTW is it possible to let BitmapHeapScan fetch tuples by TID order?
It already does ...
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose
Marc G. Fournier [EMAIL PROTECTED] writes:
On Wed, 4 May 2005, Joshua D. Drake wrote:
So where are we going?
plphp.tar.gz being seperately buildable from the core distribution,
without the core distribution source files ...
That is, plphp should build against an installed set of postgres
BTW is it possible to let BitmapHeapScan fetch tuples by TID order?
It already does ...
Oh great. It seems tbm_begin_iterate() does the trick...
--
Tatsuo Ishii
---(end of broadcast)---
TIP 7: don't forget to increase your free space map
Sergey E. Koposov [EMAIL PROTECTED] writes:
On Fri, 29 Apr 2005, Tom Lane wrote:
The latter is (or should be) doing slightly *less* work, so why is it
taking almost twice as much time? Can you get gprof profiles of the
two cases?
I've got them. I attached two files with a little bit
Hi there,
there was complain about problem with creating GiST index if
timestamp column contains 'infinity' value. The problem is indeed
exists and I'd like to have it fixed, but we have no idea
how to handle it in GiST, actually in penalty function.
Any thoughts ?
Regards,
Oleg Bartunov oleg@sai.msu.su writes:
there was complain about problem with creating GiST index if
timestamp column contains 'infinity' value. The problem is indeed
exists and I'd like to have it fixed, but we have no idea
how to handle it in GiST, actually in penalty function.
Any thoughts
PG hackers,
AndrewSN, Jim Nasby, Elein and I have been working for the last couple of
months on a new set of system views for PostgreSQL. (primarily Andrew, who
did the lion's share of the work and came up with many clever SQL
workarounds) We'd like to include them in the 8.1 release, so
Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
On Wed, 4 May 2005, Joshua D. Drake wrote:
So where are we going?
plphp.tar.gz being seperately buildable from the core distribution,
without the core distribution source files ...
That is, plphp should build against an installed set of
Josh Berkus josh@agliodbs.com writes:
As stated above, these system views, once incorporated into a pg
distribution, are likely to be with us *forever*.
I dislike to burst your bubble, but this claim is ridiculous on its
face.
We don't whack the system catalogs around from release to release
Tom,
To put it more bluntly: exactly what are you accomplishing here that
isn't already accomplished, in a *truly* standard fashion, by the
INFORMATION_SCHEMA? Why do we need yet another nonstandard view on
the underlying reality?
To quote myself:
Q: Why not just use information_schema?
A:
Joshua D. Drake [EMAIL PROTECTED] writes:
Kind of offtopic but at that point should we also include plJava?
Not decided, but it's surely on the radar screen for this discussion.
Joe Conway's PL/R is in the back of my mind as well --- it likely has
a smaller userbase than the first two, but from
Josh Berkus wrote:
PG hackers,
[snip]
What We Need From Hackers --
(other than patch approval, that is) As stated above, these system
views, once incorporated into a pg distribution, are likely to be
with us *forever*. As such, we really can't afford to do
Tom,
Not decided, but it's surely on the radar screen for this discussion.
Joe Conway's PL/R is in the back of my mind as well --- it likely has
a smaller userbase than the first two, but from a maintenance standpoint
it probably belongs on the same level.
Yeah, except PL/R has wierd build
Tim,
A nice thing to add would be a more human-comprehensible view of the
pg_locks table. I keep meaning to write a view for it myself, but
haven't ever gotten a round tuit.
Jim Nasby is working on that; see his other posts.
--
Josh Berkus
Aglio Database Solutions
San Francisco
Josh Berkus josh@agliodbs.com writes:
Joe Conway's PL/R is in the back of my mind as well
Yeah, except PL/R has wierd build requirements (FORTRAN) and different
licensing (R is GPL). :-(
[ shrug... ] All of the PLs except plpgsql require an outside language
interpreter that has its own
70 matches
Mail list logo
