On Thu, 25 Aug 2005, Josh Berkus wrote:
SavePoints be able to use within functions. ( I think this involves
making procedures that execute outside of a transaction)
Nope, supported in 8.0 for PL/pgSQL. Not sure about other languages.
You can't use savepoints, you can trap errors
Tom Lane wrote:
That won't do, as some other folks noted. But what I'd really like to
see is a hack that, when someone subscribes to a list, goes through the
moderator queue and auto-approves any pending messages from that
someone.
If it's possible, cool. What I have seen from other mailing
Well, I got all 98 tests passing on slackware 10, must be about time for RC
isn't it? :-)
Robert Treat
On Thursday 25 August 2005 19:28, Marc G. Fournier wrote:
Back on the 1st of July, after almost 6 months of development since 8.0
was released, development on 8.1 was frozen.
Now, after
Good on ya, Dave!
... John
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gavin M. Roy
Sent: Friday, August 26, 2005 1:51 PM
To: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] [ANNOUNCE] Welcome Core Team member Dave Page
Congrats Dave!
Gavin M. Roy schrieb:
Congrats Dave!
Yes, congrats!
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Aug 26, 2005, at 8:41 PM, Tino Wildenhain wrote:
Gavin M. Roy schrieb:
Congrats Dave!
Yes, congrats!
Congratulations, Dave! :)
Michael Glaesemann
grzm myrealbox com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet,
http://archives.postgresql.org/pgsql-patches/2005-08/msg00304.php
Could you perhaps test this patch as well, while you already have a
setup for testing parallel vacuums under big loads ?
I didn't find any problem with your patch during testing with 1e8 statements...
--
Teodor Sigaev
Tried doc search, pgsql-general and #postgresql.
Server: 7.4.8 on Red Hat EL4. Client psql 8.0.3 on WinXP.
Using a test server.crt and server.key, as described in 8.0 docs 16.8, I
can activate SSL encryption (WinXP 8.0.3 psql reports SSL Connection at
connect), and as expected, the server log
So, welcome Dave Page as the newest member of Core!
Congratulations Dave.!!
We memorize this day firmly. :-)
Hiroshi Saito
pgAdmin team
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Hi!
When using JDBC (8.0.311) to connect to a 8.0.3 database, with
log_duration = true
nothing happens. For psql connections, it works fine, but not for JDBC
connections. Surely a bug? Is it fixed in the 8.1 branch?
Also, as I mailed about a while back, when using prepared statements, the
Alvaro wrote:
Or, slightly different, what are people's most wanted features?
1. Proper row constructor, such that
select (1,2,1) (2,1,1);
returns the right answer,
and
select * from t where (t1,t2,t3) (c1, c2, c3) order by t1,t2,t3 limit
1
returns the right answer and uses a index on
Project members:
On behalf of the PostgreSQL Core Team, I welcome Dave Page. Dave has
been the head of the pgODBC project for a couple of years, started the
pgAdmin project in 1998, has been our lead webmaster for three years, and
is now (split with Magnus) in charge of the Win32 packaging.
Hi Marc,
can you please tell me why you changed the user/group concept to the role
concept?
I cannot see any advantages, though I see, that the complete user
administration needs to be modified when upgrading to the next version.
As I am on vacation beginning next week, please respond also to
On behalf of the PostgreSQL Core Team, I welcome Dave Page. Dave
has
been the head of the pgODBC project for a couple of years, started
the
pgAdmin project in 1998, has been our lead webmaster for three
years, and
is now (split with Magnus) in charge of the Win32 packaging. In
these
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
5. Some while later (usually several days, which means that Marc is
badly overworked :-(), the original question gets approved and
we see a duplicate appearing on the list.
The several days should be a thing of the past now. Most queues
On N, 2005-08-25 at 19:13 -0400, Alvaro Herrera wrote:
We have gone a long way now, even though it was only a year ago. My
question for everyone on this list is: What are the few remaining big
features that you see missing for PostgreSQL?
Or, slightly different, what are people's most
On R, 2005-08-26 at 16:47 +0400, Teodor Sigaev wrote:
http://archives.postgresql.org/pgsql-patches/2005-08/msg00304.php
Could you perhaps test this patch as well, while you already have a
setup for testing parallel vacuums under big loads ?
I didn't find any problem with your patch
On Thu, Aug 25, 2005 at 05:59:33PM -0700, Josh Berkus wrote:
Project members:
On behalf of the PostgreSQL Core Team, I welcome Dave Page. Dave has
been the head of the pgODBC project for a couple of years, started the
pgAdmin project in 1998, has been our lead webmaster for three years,
On Thu, Aug 25, 2005 at 07:13:18PM -0400, Alvaro Herrera wrote:
Bruce, on May 17, 2004, you wrote:
So, yea, I am frustrated. I know these features are hard and
complex, but I want them for PostgreSQL, and I want them as soon
as possible. I guess what really bugs me is that we are so
[EMAIL PROTECTED] (Alvaro Herrera) writes:
On Thu, Aug 25, 2005 at 02:45:02PM -0700, Joshua D. Drake wrote:
If y'all would like, I can eliminate the anti-virus/anti-spam checks and
just let it all go through though ... *evil grin*
Would not bother me in the least. I have protective
* Alvaro Herrera ([EMAIL PROTECTED]) wrote:
Or, slightly different, what are people's most wanted features?
MERGE.
Stephen
signature.asc
Description: Digital signature
Dennis Bjorklund wrote:
On Thu, 25 Aug 2005, Josh Berkus wrote:
SavePoints be able to use within functions. ( I think this involves
making procedures that execute outside of a transaction)
Nope, supported in 8.0 for PL/pgSQL. Not sure about other languages.
You can't
On Fri, Aug 26, 2005 at 11:42:04AM -0400, Chris Browne wrote:
[EMAIL PROTECTED] (Alvaro Herrera) writes:
On Thu, Aug 25, 2005 at 02:45:02PM -0700, Joshua D. Drake wrote:
If y'all would like, I can eliminate the anti-virus/anti-spam
checks and just let it all go through though ... *evil
On Fri, 2005-08-26 at 13:13 -0400, Nicholas Walker wrote:
You can't use savepoints, you can trap errors which is implemented using
savepoints. You still might want to write code like this:
BEGIN
SAVEPOINT foo;
IF SOME_ERROR_CODE = 1234 THEN
ROLLBACK TO SAVEPOINT
On Thu, 25 Aug 2005, Alvaro Herrera wrote:
Or, slightly different, what are people's most wanted features?
Since you asked:
* concurrent, partial vacuum that would for example only scan pages that
happen to be in memory
* index-only scans
* database assertions
* lightwight PITR that
Finded problem in GiST isn't too simple to resolve. I'm working on it. The
problem is about update query...
Tom Lane wrote:
Teodor Sigaev [EMAIL PROTECTED] writes:
http://www.sigaev.ru/gist/concur.pl
http://www.sigaev.ru/gist/concur.sh
BTW, these scripts seem to indicate that there's a
Alvaro Herrera wrote:
Or, slightly different, what are people's most wanted features?
Things I would have found useful in the past year or so include:
Standards stuff:
* Updateable views (easier to use Ruby/Rails's ActiveRecord on legacy data)
* The elementary OLAP stuff
Contrib related
Hi all,
Our organizations are doing a lot of real time reporting involving
queries with multiple tables, and large tables. I found that two
features are very nice to have:
- Table Partition
- Materialized view
Thanks,
J
On 8/26/05, Ron Mayer [EMAIL PROTECTED] wrote:
Alvaro Herrera wrote:
Great updates! Let me comment on each one.
I made a pass over the TODO list to see what was out of date.
* Allow administrators to safely terminate individual sessions either
via an SQL function or SIGTERM
Currently SIGTERM of a backend can lead to lock table corruption.
I see the latest buildfarm result from a mipsel machine is failing:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=lionfishdt=2005-08-26%2005:30:07
and the failure is this:
TRAP: FailedAssertion(!(lock-shared 0), File: lwlock.c, Line: 456)
LOG: server process (PID 10112) was terminated by
Merlin Moncure Wrote:
... Be sure to mix in a request for
better Unicode support at the same time, Dave loves that.
As do I... :)
... John
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
Alvaro Herrera wrote:
On Thu, Aug 25, 2005 at 01:53:32PM -, Greg Sabino Mullane wrote:
Tom Lane asked:
o Improve psql's handling of multi-line queries
Uh, what's wrong with it? This item seems far too vague.
I think perhaps this means adding multi-line support to
Hannu Krosing wrote:
On K, 2005-08-24 at 21:58 -0400, Tom Lane wrote:
* %Allow TRUNCATE ... CASCADE/RESTRICT
Huh? What would that do?
Maybe this was meant truncating of tables with dependent foreign keys ?
AFAIR this was solved by allowing truncating several tables in one
command
Jim C. Nasby wrote:
I *think* this is reffering to how pg_dump makes some assumptions about
what things are system objects.
http://archives.postgresql.org/pgsql-committers/2005-08/msg00203.php
doesn't help a heck of a lot...
Can we add an interface to the TODO list that contains search
Tom Lane wrote:
Ron Mayer [EMAIL PROTECTED] writes:
The most unambiguous behavior would be to not have
commented out values in the config file at all.
Yeah, Robert Treat suggested that upthread, and I think it's been pushed
by others too.
The only argument I can see against it is that
Andrew Dunstan wrote:
Tom Lane wrote:
Or perhaps use a different separator:
junk=# select * from xyz;
id |name| address | del_addr
++---+--
1 | Joe Bloggs
Ron Mayer wrote:
* more sane math with intervals. For example, try:
select '0.01 years'::interval, '0.01 months'::interval;
Added to TODO:
Fix SELECT '0.01 years'::interval, '0.01 months'::interval;
--
Bruce Momjian| http://candle.pha.pa.us
Tom Lane wrote:
I see the latest buildfarm result from a mipsel machine is failing:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=lionfishdt=2005-08-26%2005:30:07
and the failure is this:
TRAP: FailedAssertion(!(lock-shared 0), File: lwlock.c, Line: 456)
LOG: server process (PID
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
Tom Lane wrote:
which makes it seem highly probable that this recently committed patch
to convert the MIPS out-of-line spinlock code into inline assembler
isn't right:
http://archives.postgresql.org/pgsql-committers/2005-08/msg00319.php
As the
-Original Message-
From: Merlin Moncure [mailto:[EMAIL PROTECTED]
Sent: 26 August 2005 15:42
To: pgsql-hackers@postgresql.org
Cc: Dave Page
Subject: RE: [HACKERS] [ANNOUNCE] Welcome Core Team member Dave Page
Congratulations, dave. We should probably be cross-posting
this
-Original Message-
From: John Hansen [mailto:[EMAIL PROTECTED]
Sent: 26 August 2005 20:03
To: Merlin Moncure; pgsql-hackers@postgresql.org
Cc: Dave Page
Subject: RE: [HACKERS] [ANNOUNCE] Welcome Core Team member Dave Page
Merlin Moncure Wrote:
... Be sure to mix in a
I wrote:
Can anyone spot the problem? If not I fear we'll have to revert this.
After a bit of reading MIPS documentation, I found out that the proposed
patch is exactly backward: it returns 1 if it gets the lock and 0 if the
lock is already held :-(
Because callers will loop on a nonzero
Josh Berkus josh@agliodbs.com writes:
Oh, yeah I forgot:
-- windowing functions (e.g. RANK, RANK OVER, LAST 10)
Include this URL or one like it in any TODO about this:
http://publib.boulder.ibm.com/infocenter/rb63help/topic/com.ibm.redbrick.doc6.3/sqlrg/sqlrg36.htm#sii-06-62323
It would
Jim,
Spikewatch is testing a number of different open-source components,
including ours. If you click on a green datapoint, you can see what our
actual code-coverage was for that test (presumably they're running the
regression tests). Unfortunately, the banner ad I saw for them showed
MySQL
On Fri, Aug 26, 2005 at 03:44:18PM -0400, Bruce Momjian wrote:
Jim C. Nasby wrote:
I *think* this is reffering to how pg_dump makes some assumptions about
what things are system objects.
http://archives.postgresql.org/pgsql-committers/2005-08/msg00203.php
doesn't help a heck of a
Bruce Momjian pgman@candle.pha.pa.us writes:
Ron Mayer wrote:
* more sane math with intervals. For example, try:
select '0.01 years'::interval, '0.01 months'::interval;
Added to TODO:
Fix SELECT '0.01 years'::interval, '0.01 months'::interval;
Arguably, both of those things should be
What everybody else said. :) But if it comes to voting...
Anything to improve parallelism is good.
Anything reducing blocking (ie: CLUSTER, VACUUM FULL) is good
Improved handling of sort_mem (I think this will hit bizgres first)
merge :)
STATISTICS ON INDEXES! (specifically multi-field indexes)
Josh Berkus wrote:
Is it worth trying to promote this as a way to promote PostgreSQL? Also,
is it worth trying to improve our test coverage?
Actually, they'll be running a contest (with prizes up to $2500) for
improved test coverage for OSS applications. I've been trying to get
On Fri, Aug 26, 2005 at 01:49:34PM -0700, Josh Berkus wrote:
Jim,
Spikewatch is testing a number of different open-source components,
including ours. If you click on a green datapoint, you can see what our
actual code-coverage was for that test (presumably they're running the
regression
Jim,
Can anyone step up for this now that things will hopefully calm down a
bit during beta? IIRC you just needed a commitment from a commiter,
right?
Pretty much. Also, we need to write up test submission guidelines:
basically just documentation on how to create a new regression test.
Running EXPLAIN on a view that has an aggregate and uses an index
results in the error bogus varno: 5. At least I think the aggregate
and index are necessary -- removing either from the following example
allows EXPLAIN to succeed:
test= CREATE TABLE foo (x integer);
CREATE TABLE
test= CREATE
Tom Lane wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
Ron Mayer wrote:
* more sane math with intervals. For example, try:
select '0.01 years'::interval, '0.01 months'::interval;
Added to TODO:
Fix SELECT '0.01 years'::interval, '0.01 months'::interval;
Arguably, both
52 matches
Mail list logo