On Wed, Aug 24, 2005 at 12:26:21AM -0400, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > Is the intention that standard_conforming_strings will always be
> > read-only?
>
> For the moment it's read-only false; the long-term goal is that it will
> be read-only true. In between we
On Mon, Aug 22, 2005 at 07:09:10PM -0400, Bruce Momjian wrote:
> Jim C. Nasby wrote:
> > Can someone turn these items into a "beginning hacker's TODO" as has
> > been discussed before? Or find a way to mark them on the main TODO?
> >
> > If someone wants to tell me how this should be done and give
While marking up TODO for potential new-hacker items I've run across
some items that probably need more explanation:
o Allow commenting of variables in postgresql.conf to restore them
to defaults
This doesn't work already?
* Allow triggers to be disabled [trigger]
Isn't this going to
On Mon, Aug 22, 2005 at 06:48:52PM -0400, Rod Taylor wrote:
> Another source of items on the TODO list is the Unsupported Features
> portion of the SQL Conformance documentation:
>
> http://www.postgresql.org/docs/8.0/interactive/unsupported-features-sql-standard.html
Maybe we should just have a
Bruce Momjian schrob:
> Stephen Frost wrote:
> -- Start of PGP signed section.
>> * Jim C. Nasby ([EMAIL PROTECTED]) wrote:
>> > On Thu, Jul 07, 2005 at 01:48:59PM -0400, Tom Lane wrote:
>> > > I don't really agree with the viewpoint that truncate is just a quick
>> > > DELETE, and so I do not agr
Michael Fuhr <[EMAIL PROTECTED]> writes:
> I see in gram.y that SHOW and RESET take a ColId but SET takes a
> var_name, which is ColId or var_name.ColId. Is there a reason for
> the inconsistency or is it just an oversight?
Offhand it looks like the custom-variable patch missed dealing
with SHOW
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> Is the intention that standard_conforming_strings will always be
> read-only?
For the moment it's read-only false; the long-term goal is that it will
be read-only true. In between we will have a release or three where it
is modifiable to some extent.
SHOW and RESET require quoting in cases where SET doesn't:
test=> SHOW plperl.use_strict;
ERROR: syntax error at or near "." at character 12
LINE 1: SHOW plperl.use_strict;
^
test=> SHOW "plperl.use_strict";
plperl.use_strict
---
on
(1 row)
test=> SET plperl
Josh Berkus wrote:
> Satoshi, if you can package up a patch on current CVS, I'll throw it at DBT2.
Ok. I'll do it.
--
NAGAYASU Satoshi <[EMAIL PROTECTED]>
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
Thanks, done.
---
Marko Kreen wrote:
> On Tue, Aug 23, 2005 at 05:25:56PM -0400, Bruce Momjian wrote:
> > Thanks, updated. I suspected there was more than I had listed.
>
> This patch tidies dots and bit more.
>
> --
> ma
Thanks, fixed.
---
Darcy Buskermolen wrote:
> On Monday 22 August 2005 20:16, Bruce Momjian wrote:
> > I have compiled the 8.1 release notes and converted them to SGML at:
> >
> > http://candle.pha.pa.us/main/writings/pgsq
On Tue, Aug 23, 2005 at 05:25:56PM -0400, Bruce Momjian wrote:
> Thanks, updated. I suspected there was more than I had listed.
This patch tidies dots and bit more.
--
marko
Index: doc/src/sgml/release.sgml
===
RCS file: /opt/arc/c
On Monday 22 August 2005 20:16, Bruce Momjian wrote:
> I have compiled the 8.1 release notes and converted them to SGML at:
>
> http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
>
> I still need to add markup and cleanup, but it is good enough for
> review and for beta1.
On Monday 22 August 2005 20:16, Bruce Momjian wrote:
> I have compiled the 8.1 release notes and converted them to SGML at:
>
> http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
>
> I still need to add markup and cleanup, but it is good enough for
> review and for beta1.
Thanks, updated. I suspected there was more than I had listed.
---
Marko Kreen wrote:
> On Tue, Aug 23, 2005 at 03:51:35PM -0400, Bruce Momjian wrote:
> > I have finished working on the release notes for the moment:
> >
> >
Stephen Frost wrote:
-- Start of PGP signed section.
> * Bruce Momjian (pgman@candle.pha.pa.us) wrote:
> > http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
>
> Regarding E.1.3.4 (Object Manipulation Changes):
>
> -
> Allow ALTER OWNER commands to be performed by
Jim C. Nasby wrote:
> Just so this doesn't get lost (and I don't forget):
>
> Is the intention that standard_conforming_strings will always be
> read-only? ISTM it would be very useful if it was used to control the
> behavior of strings that weren't E quoted while people are
> transitioning. Or is
On Tue, Aug 23, 2005 at 03:51:35PM -0400, Bruce Momjian wrote:
> I have finished working on the release notes for the moment:
>
> http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
>
> I will update them just before we put out the beta.
Here's bit clarified pgcrypto summ
* Bruce Momjian (pgman@candle.pha.pa.us) wrote:
> http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
Regarding E.1.3.4 (Object Manipulation Changes):
-
Allow ALTER OWNER commands to be performed by the object owner as well
as the superuser (Stephen Frost)
Prior r
Just so this doesn't get lost (and I don't forget):
Is the intention that standard_conforming_strings will always be
read-only? ISTM it would be very useful if it was used to control the
behavior of strings that weren't E quoted while people are
transitioning. Or is that too difficult to do?
(Unf
On Tue, Aug 23, 2005 at 03:57:52PM -0400, Bruce Momjian wrote:
> Jim C. Nasby wrote:
> > On Mon, Aug 22, 2005 at 11:16:14PM -0400, Bruce Momjian wrote:
> > > I have compiled the 8.1 release notes and converted them to SGML at:
> > >
> > >
> > > http://candle.pha.pa.us/main/writings/pgsql/sgml/r
It'd also be good to add
http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
to the page.
On Tue, Aug 23, 2005 at 01:38:53PM +0200, Magnus Hagander wrote:
> > I have put together a new web page to show all the PostgreSQL
> > status pages I maintain, and I have added a "bugs
Jim C. Nasby wrote:
> On Mon, Aug 22, 2005 at 11:16:14PM -0400, Bruce Momjian wrote:
> > I have compiled the 8.1 release notes and converted them to SGML at:
> >
> > http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
> >
> > I still need to add markup and cleanup, but it
On Mon, Aug 22, 2005 at 11:16:14PM -0400, Bruce Momjian wrote:
> I have compiled the 8.1 release notes and converted them to SGML at:
>
> http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
>
> I still need to add markup and cleanup, but it is good enough for
> review and
I have finished working on the release notes for the moment:
http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
I will update them just before we put out the beta.
--
Bruce Momjian| http://candle.pha.pa.us
pgman@candle.pha.pa.us
On Mon, Aug 22, 2005 at 10:18:25PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > ... But I agree with Satoshi; if there are
> > people who will benefit from this option (which doesn't hurt those who
> > choose not to use it), why not put it in?
>
> Because there's no such
On Tue, Aug 23, 2005 at 09:26:07AM +0800, William ZHANG wrote:
> ""Jim Nasby"" <[EMAIL PROTECTED]> write
> > Yes, but it doesn't really specify if you have to have a privilege in
> > order to grant it, although reading one of the notes[1] tends to indicate
> > that you must have a role in order t
On Mon, Aug 22, 2005 at 10:42:15PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > My original point was that if you don't have permission to do something,
> > you shouldn't be able to grant permissions to do it. This applies to all
> I'm not convinced. It seems reasonable
The documentation already says prominently that roles and users are
the same thing. If you're fooling with CREATE ROLE without having
read any of that, I'm not sure that an error message will help.
I am talking about consistency here. Most people are not
going to think a role is a user, at
Andrew Dunstan wrote:
>
>
> Bruce Momjian wrote:
>
> >I have compiled the 8.1 release notes and converted them to SGML at:
> >
> > http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
> >
> >I still need to add markup and cleanup, but it is good enough for
> >review and for
I wrote:
> (Just looking at it again, the code in convert_string_to_scalar is
> pretty bogus for multibyte encodings in any case. Possibly we need to
> rethink the whole approach.)
After studying this some more, I think the code is really so bogus for
any non-ASCII situation that it's probably no
Jim,
> But have you looked at how this affects response time, especially around
> checkpoints? Testing I've done shows that changing the variables in
> 8.0.3 can markedly reduce the impact of checkpoints. In many
> applications, maintaining low response times is more important than
> overall throu
Bruce Momjian wrote:
. pl/perl support for strict mode
That was completed after I pulled CVS, I think. It will be updated
later.
Actually, it snuck in with one of Abhijit's patches.
And I am not sure if this counts as a bug fix or a feature :-) :
. pl/perl logging of non-fat
Jim, Satoshi,
> It should be possible to see what the crossover point is in terms of
> benefit using dbt2 and tweaking the transactions that are run, something
> I can do if there's interest. But I agree with Satoshi; if there are
> people who will benefit from this option (which doesn't hurt thos
Added. Thanks.
---
Andrew Dunstan wrote:
>
>
> Bruce Momjian wrote:
>
> >>
> >>. pl/perl support for strict mode
> >>
> >>
> >
> >That was completed after I pulled CVS, I think. It will be updated
> >later.
> >
> >
Michael Paesold <[EMAIL PROTECTED]> writes:
> These I don't really understand:
> - Improve rtree index capabilities and performance (Neil)
> - Replace rtree index code with code from /contrib/rtree_gist (Tom)
Not sure how Bruce got the latter out of this commit message:
Migrate rtree_gist
OK, updated. When I read "migrate" I thought "move".
---
Tom Lane wrote:
> Michael Paesold <[EMAIL PROTECTED]> writes:
> > These I don't really understand:
> > - Improve rtree index capabilities and performance (Neil)
> > -
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> There is a strxfrm() call in
>> src/backend/utils/adt/selfuncs.c, which probably needs to be
>> looked at too.
> Ok. Will look into that. Do you have a hint as to how to test that?
Any problems would manifest as a bogus interpolation between hist
Fixed.
---
Havasv?lgyi Ott? wrote:
> Bruce,
>
> I have also noticed a small error:
>
> a.. Remove old *.backup files when we do pg_stop_backup() (Bruce)
>
> a.. This prevents a large number of *.backup files from existing
Michael Paesold wrote:
> Bruce Momjian wrote:
> > I have compiled the 8.1 release notes and converted them to SGML at:
> >
> > http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
> >
> > I still need to add markup and cleanup, but it is good enough for
> > review and for b
Bruce Momjian wrote:
I have compiled the 8.1 release notes and converted them to SGML at:
http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
I still need to add markup and cleanup, but it is good enough for
review and for beta1. I will work on it more tomorrow.
Bruce,
I have also noticed a small error:
a.. Remove old *.backup files when we do pg_stop_backup() (Bruce)
a.. This prevents a large number of *.backup files from existing in
pg_xlog/.
I think there should not be a point on the left of the second line because
it's the details of the first
> I have put together a new web page to show all the PostgreSQL
> status pages I maintain, and I have added a "bugs to be fixed
> in 8.1" page that will track must-fix bugs for this release.
> It is at:
>
> http://momjian.postgresql.org/pgrelease
>
> I think this should be added to the
Thanks, added.
---
Dave Page wrote:
> Hi Bruce,
>
> Andreas did the initial version of the dbsize integration patch so should be
> included in the credit for that item.
>
> Regards, Dave
>
>
> -Original Message-
Hi Bruce,
Andreas did the initial version of the dbsize integration patch so should be
included in the credit for that item.
Regards, Dave
-Original Message-
From: "Bruce Momjian"
Sent: 23/08/05 04:19:19
To: "PostgreSQL-development"
Subject: [HACKERS] 8.1 release notes
I have compiled
""Jim Nasby"" <[EMAIL PROTECTED]> write
> Yes, but it doesn't really specify if you have to have a privilege in
> order to grant it, although reading one of the notes[1] tends to indicate
> that you must have a role in order to grant it. Unless I'm overlooking
> some part of the docs?
I am conf
Fixed.
---
Bruno Wolff III wrote:
> On Mon, Aug 22, 2005 at 23:16:14 -0400,
> Bruce Momjian wrote:
> > I have compiled the 8.1 release notes and converted them to SGML at:
> >
> > http://candle.pha.pa.us/main/writings/
Fixed.
---
Mario Weilguni wrote:
> JFYI:
>
> "Allow indexes to be used for MIN/MAX (Tom)
>
> In previous releases, the only way to use index for MIN/MAX was to
> rewrite the query as SELECT col FROM tab ORDER BY col LIMIT
Thanks, added.
---
Oleg Bartunov wrote:
> Bruce,
>
> I think I took part in GiST concurrency and recovery project.
>
> Oleg
> On Mon, 22 Aug 2005, Bruce Momjian wrote:
>
> > I have compiled the 8.1 release notes and
I have committed changes that I believe fix this problem:
http://archives.postgresql.org/pgsql-committers/2005-08/msg00213.php
But it needs more testing. Would you update to CVS tip and see if you
still see the failure?
It seems, patch works correctly. My tests is passed with approximatly 1e8 S
.. back home again after a couple of days ..
> >> I am unsure of how to proceed. As I see it there are three paths:
> >> 1) Use native win32 functionality only on win32
> >> 2) Use ICU functionality only on win32
> >> 3) Allow both ICU and native functionality, compile time
> >>switch --wit
On Aug 23, 2005, at 6:07 PM, Michael Paesold wrote:
"This caused CREATE DATABASE to sometimes fail because a new
database can not be created if anyone else is in the template
database."
Shouldn't this read:
"This caused CREATE DATABASE to sometimes fail because a new
database could not be
Bruce Momjian wrote:
I have compiled the 8.1 release notes and converted them to SGML at:
http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
I still need to add markup and cleanup, but it is good enough for
review and for beta1. I will work on it more tomorrow.
I thi
JFYI:
"Allow indexes to be used for MIN/MAX (Tom)
In previous releases, the only way to use index for MIN/MAX was to
rewrite the query as SELECT col FROM tab ORDER BY col LIMIT 1. This not
happens automatically."
I guess this should read "This now happens automatically"
Regards,
Mario W
Bruce,
I think I took part in GiST concurrency and recovery project.
Oleg
On Mon, 22 Aug 2005, Bruce Momjian wrote:
I have compiled the 8.1 release notes and converted them to SGML at:
http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
I still need to add mark
On E, 2005-08-22 at 23:17 +0300, Hannu Krosing wrote:
> On E, 2005-08-22 at 14:05 -0400, Tom Lane wrote:
> > Hannu Krosing <[EMAIL PROTECTED]> writes:
> > > But I could not find the breakage (from your Aug 17 email) with
> >
> > >> You missed vac_truncate_clog, though.
> >
> > That was fixed (an
Jim C. Nasby wrote:
It should be possible to see what the crossover point is in terms of
benefit using dbt2 and tweaking the transactions that are run, something
I can do if there's interest. But I agree with Satoshi; if there are
people who will benefit from this option (which doesn't hurt thos
57 matches
Mail list logo
