Tom Lane wrote:
Oliver Jowett <[EMAIL PROTECTED]> writes:
What about refusing to change client_encoding to something other than
SQL_ASCII on SQL_ASCII databases?
Not sure that would do anything very useful. People who aren't thinking
about this probably aren't thinking about setting client_encod
I think we need to deny changing column types if a function is using the
table type as a return set.
test=# create table test (a int4);
CREATE TABLE
test=# create function test () returns setof test as 'select 1' language
sql;
CREATE FUNCTION
test=# alter table test alter a type bigint;
ALTER TA
Bruce Momjian <[EMAIL PROTECTED]> writes:
> > . Allow multi-column indexes to be used to optimize row-value expressions. Ie,
> > allow a btree index on a,b to be used to execute an expression like (a,b) <
> > (x,y).
>
> I have not heard of any of those so I have not been actively excluding
>
Christopher Kings-Lynne wrote:
People have been complaining (not without reason) that without any
documentation they can hardly test the new PITR code. I have hacked
up and committed some rough docs that should be enough for testing.
They're on-line now at
http://candle.pha.pa.us/main/writings/pgs
On Tue, 3 Aug 2004, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > On Tue, Aug 03, 2004 at 10:17:14AM -0400, Tom Lane wrote:
> >> Right. Essentially, our implementation is supplying the SAVEPOINT and
> >> ROLLBACK TO commands implicitly as part of any block with an EXCEPTION
> >
Certainly gave me a chuckle. Technical documentation with humour...now the
product has *everything*.
Mark
Quoting Tom Lane <[EMAIL PROTECTED]>:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> > I love this:
>
> > "The ability to restore the database to a previous point in time creates
>
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Here are the open items. They all have to be addressed before final,
> but not all before beta starts.
>P O S T G R E S Q L
> 7 . 5 O P E NI T E M S
Well, we could start with s/7.5/8.0/ ...
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> I love this:
> "The ability to restore the database to a previous point in time creates
> some complexities that are akin to science-fiction stories about time
> travel and parallel universes."
Well, the code *works* but I'm not entirely sur
Changing to a domain and back doesn't do dependencies correctly:
test=# create table parent (a int4);
CREATE TABLE
test=# drop table parent;
DROP TABLE
test=# drop domain dom;
DROP DOMAIN
test=# create table parent (a int4);
CREATE TABLE
test=# create domain dom as bigint;
CREATE DOMAIN
test=# alte
Bruce Momjian <[EMAIL PROTECTED]> writes:
> One issue is that we now have to update the PG_VERSION file in /data
> (via configure.in) so we will be forcing an initdb when we make the
> change.
I'll take care of it tomorrow ... we definitely want to deal with all
the known initdb-forcing reasons be
"Scott Marlowe" <[EMAIL PROTECTED]> writes:
> On Tue, 2004-08-03 at 13:05, CSN wrote:
> > Just wondering, is updateable views slated for a
> > future version of Postgresql? In addition to using
> > rules that is.
>
> I would think that a basic fleshing out of the logic with some kind of
> stored
Here are the open items. They all have to be addressed before final,
but not all before beta starts.
---
P O S T G R E S Q L
7 . 5 O P E NI T E M S
Current at
I thought Simon was going to give us some docs for PITR. Did he or did
you have to write up your own?
---
Tom Lane wrote:
> People have been complaining (not without reason) that without any
> documentation they can hardly
Gaetano Mendola wrote:
> After two series 7.3 and 7.4 that ignore the force argument,
> why don't remove it in the 8.0 ?
>
Well, we can certainly remove the documentation for it at least.
Comments?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED]
Gaetano Mendola wrote:
> After two series 7.3 and 7.4 that ignore the force argument,
> why don't remove it in the 8.0 ?
Thinking about it, REINDEX FORCE is hardly a regularly used command and
we could probably remove the whole thing.
--
Bruce Momjian| http://candle.ph
Tom Lane wrote:
> Joe Conway <[EMAIL PROTECTED]> writes:
> > One question did arise, however. In order to use pgxs I needed to do:
> >make install-all-headers
> > instead of:
> >make install
>
> > I seem to recall some discussion about this, but at the time didn't
> > realize the impact.
Greg Stark wrote:
>
> Bruce Momjian <[EMAIL PROTECTED]> writes:
>
> > TODO item?
>
> On that note several prior conversations I had here ended with WIBNI
> conclusions that really ought to be TODO items, in my humble opinion. Two come
> to mind off the top of my head resulting in:
>
> . "SELECT
People have been complaining (not without reason) that without any
documentation they can hardly test the new PITR code. I have hacked
up and committed some rough docs that should be enough for testing.
They're on-line now at
http://candle.pha.pa.us/main/writings/pgsql/sgml/backup-online.html
and
Tom Lane wrote:
> Jan Wieck <[EMAIL PROTECTED]> writes:
> > Having done something similar for the SPI manager once, so that
> > parameters can have unknown type and the code calling SPI_prepare() will
> > find the chosen types in the type array, so that the code calling
> > SPI_execp() can do th
However, we could certainly talk about altering the default behavior
(eg, install becomes install-no-headers and install-all-headers becomes
part of the default install target).
Seems like a good idea to me.
Chris
---(end of broadcast)---
TIP 9: the p
BEGIN;
SAVEPOINT start;
INSERT INTO users VALUES(user || suffix);
EXIT;
EXCEPTION
WHEN UNIQUE_VIOLATION THEN
ROLLBACK TO start;
Depending on how tense you want to be about Oracle compatibility, we
could make people actually write their blocks as above --- that is,
the SAVEPOINT and ROLLBACK commands would be a required part of the
exception-block syntax. They wouldn't actually *do* anything, but
they would make the code lo
I'm not really keen on this idea unless you're eager to make a 5-year
commitment to maintain the code. The load formats of other RDBMSes change
all the time -- MySQL is a particularly egregious example, with 2
incompatible changes in the last year -- and it would become a pain to keep
track.
One issue is that we now have to update the PG_VERSION file in /data
(via configure.in) so we will be forcing an initdb when we make the
change.
Should we go ahead and make these changes now?
---
Tom Lane wrote:
> The recen
Joe Conway <[EMAIL PROTECTED]> writes:
> One question did arise, however. In order to use pgxs I needed to do:
>make install-all-headers
> instead of:
>make install
> I seem to recall some discussion about this, but at the time didn't
> realize the impact. IMHO pgxs support (including all
People have been complaining (not without reason) that without any
documentation they can hardly test the new PITR code. I have hacked
up and committed some rough docs that should be enough for testing.
They're on-line now at
http://candle.pha.pa.us/main/writings/pgsql/sgml/backup-online.html
and
Tom Lane wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
In addition to the ecpg warnings mentioned by Tom, I'm also seeing
compile warnings wrt plpython:
make[3]: Entering directory `/opt/src/pgsql-cvs/pgsql-7.5/src/pl/plpython'
gcc -O2 -fno-strict-aliasing -g -Wall -Wmissing-prototypes
-Wmissing
Joe Conway wrote:
> One question did arise, however. In order to use pgxs I needed to do:
>make install-all-headers
> instead of:
>make install
Yes, I forgot to mention that the install targets still need to be
sorted out. FWIW, I've always been in favor of installing everything
all the
First of all "promised at OSCON to fix" is a bit exaggerated. I said I
will look into the issue and see what can be done.
Having done something similar for the SPI manager once, so that
parameters can have unknown type and the code calling SPI_prepare() will
find the chosen types in the type ar
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> On Tue, Aug 03, 2004 at 10:17:14AM -0400, Tom Lane wrote:
>> Right. Essentially, our implementation is supplying the SAVEPOINT and
>> ROLLBACK TO commands implicitly as part of any block with an EXCEPTION
>> clause. When we get around to updating the "
> It`s not a beta-blocker, but I still need to fix the postgresql.conf.sample
> file to not use all those commented-out values. Unfortunately, I have not
> had time to do this. If someone could take of this, it would be most
> appreciated. See Tom`s notes on some issues involved:
>
> http://archi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm not able to reproduce it anymore but I seen this after a
deadlock detection involving a subtransaction:
ERROR: deadlock detected
DETAIL: Process 31330 waits for ShareLock on transaction 570; blocked by process
31328.
Process 31328 waits f
On Tuesday 03 August 2004 11:46 am, Tom Lane wrote:
> Jan Wieck <[EMAIL PROTECTED]> writes:
> > Having done something similar for the SPI manager once, so that
> > parameters can have unknown type and the code calling SPI_prepare()
> > will find the chosen types in the type array, so that the code
On Tuesday 03 August 2004 08:18 am, Tom Lane wrote:
> "Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> > Second, Jan promised at OSCON to fix up server-side prepare so it
> > actually works even if you do not have the exact types to pass in. I
> > presume you will then be able to do something li
Jan Wieck <[EMAIL PROTECTED]> writes:
> Having done something similar for the SPI manager once, so that
> parameters can have unknown type and the code calling SPI_prepare() will
> find the chosen types in the type array, so that the code calling
> SPI_execp() can do the appropriate type casting
Hi all,
I'm reading some comment on CVS and I seen this comment
for tab-complete.c revision 1.109:
Fix subtransaction behavior for large objects, temp namespace, files,
password/group files. Also allow read-only subtransactions of a read-write
parent, but not vice versa. These are the reasonably
After two series 7.3 and 7.4 that ignore the force argument,
why don't remove it in the 8.0 ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAI
On Tue, Aug 03, 2004 at 10:17:14AM -0400, Tom Lane wrote:
> Gavin Sherry <[EMAIL PROTECTED]> writes:
>
> > BEGIN;
> > SAVEPOINT start;
> > INSERT INTO users VALUES(user || suffix);
> > EXIT;
> > EXCEPTION
> >
I have on my todo an item regarding arrays with a dimension lower bound
of something other than one. The issue is that when stored, dumped, and
then reloaded, the array lower bound is reset to 1. Example:
create table foo(f1 int[]);
insert into foo values(array[1]);
update foo set f1[-1:0] = arr
The upsides, as I see them:
They use one system for handling all exceptions, user generated or not.
They didn't come up with their own arbitrary names for all the error
codes they have. Naming an exception follows all the namespace rules;
for example, the exception code example I gave was in the
Peter Eisentraut wrote:
Am Freitag, 16. Juli 2004 16:34 schrieb Fabien COELHO:
Please find attached another new version of a patch which provides a
working infrastructure for pg extensions. I hope it addresses all of
Peter's comments. I'll be away for the next 3 weeks, so if minor changes
are requi
Gavin Sherry <[EMAIL PROTECTED]> writes:
> On Tue, 3 Aug 2004, Jeff Davis wrote:
>> I have a question for you also. I just posted a patch at about the same
>> time you did (I sent it to pgsql-patches, but I haven't seen it appear
>> yet). Mine was a one-liner (appended to end of this email) and all
Chris,
> I was thinking a pg_export utility that can output to a range of other
> databases SQL formats would also be a good idea. It would share about
> 90% of the pg_dump code, but I'm trying to think of how to avoid
> duplicating the code.
I'm not really keen on this idea unless you're eager
Devrim GUNDUZ <[EMAIL PROTECTED]> writes:
> Are these all intended behaviors?
Yes. Rolling back to a savepoint doesn't release the savepoint. See
http://developer.postgresql.org/docs/postgres/sql-savepoint.html
http://developer.postgresql.org/docs/postgres/sql-rollback-to.html
http://developer.p
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> Second, Jan promised at OSCON to fix up server-side prepare so it actually
> works even if you do not have the exact types to pass in. I presume you
> will then be able to do something like this:
> PREPARE mystatement AS SELECT * FROM pg_class WHE
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Before 7.4, to be handled by regex routines, UTF-8 are converted to
> ISO 10646. There was a limitaion in regex routines in that they cannot
> handle multibyte characters > 2bytes. In another word only 16bit UCS-2
> are supported. That's why ISO 10646 > 0x
Gavin Sherry <[EMAIL PROTECTED]> writes:
> BEGIN;
> SAVEPOINT start;
> INSERT INTO users VALUES(user || suffix);
> EXIT;
> EXCEPTION
> WHEN UNIQUE_VIOLATION THEN
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Tue, 3 Aug 2004, Merlin Moncure wrote:
> > test=# ROLLBACK to devrim;
> > ROLLBACK
> >
> > ...and it goes on forever. Is it a feature or a bug?
>
> feature. You can rollback to a savepoint multiple times (0 or more
> savepoints might inter
Gavin Sherry <[EMAIL PROTECTED]> writes:
> I agree with you that forcing users to declare names for SQLCODEs is not
> such a great idea. What I do like, however, is the ability to declare your
> own exceptions. For example:
Agreed, that would be a good thing to have, but I think it's something
we'
> test=# ROLLBACK to devrim;
> ROLLBACK
> test=# ROLLBACK to devrim;
> ROLLBACK
>
> ...and it goes on forever. Is it a feature or a bug?
>
feature. You can rollback to a savepoint multiple times (0 or more
savepoints might intervene)
> Are these all intended behaviors? I thought we wouldn't b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I updated the CVS a few minutes before, applied Gavin Sherry's latest
xact patch. It worked.
Anyway...here is what I did:
==Case 1=
test=# BEGIN ;
BEGIN
test=# SAVEPOINT devrim;
SAVEPOINT
test=#
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Here are the open items. I think once they are resolved we can head
> into beta:
>...
> Does anyone have any more?
Two more:
It`s not a beta-blocker, but I still need to fix the postgresql.conf.sample
file to not use all those commented-out
> In src/backend/utils/mb/wchar.c there is a check to exclude Unicode
> characters above 0x1. I can't see anything to explain this
> restriction, except possibly this in the release notes for 7.2:
>
> Reject invalid multibyte character sequences (Tatsuo)
>
> It does not explain why p
One other difference when compared with Oracle is that Oracle does not
abort the transaction which raised the exception. Although I generally do
not think this is a great idea, it does allow for things like retry loops.
Assuming we have savepoints, consider the following function which creates
a us
On Tue, 3 Aug 2004, Jeff Davis wrote:
> On Tue, 2004-08-03 at 03:41, Gavin Sherry wrote:
> > Attached is a patch fixing this.
> >
> > One question I do have:
> >
> > if (target->savepointLevel != s->savepointLevel)
> >
> > Will this ever be true in the current code? I cannot see anything setti
In src/backend/utils/mb/wchar.c there is a check to exclude Unicode
characters above 0x1. I can't see anything to explain this
restriction, except possibly this in the release notes for 7.2:
Reject invalid multibyte character sequences (Tatsuo)
It does not explain why part of the Uni
On Tue, 2004-08-03 at 03:41, Gavin Sherry wrote:
> Attached is a patch fixing this.
>
> One question I do have:
>
> if (target->savepointLevel != s->savepointLevel)
>
> Will this ever be true in the current code? I cannot see anything setting
> savepointLevel explicitly.
>From reading the
Attached is a patch fixing this.
One question I do have:
if (target->savepointLevel != s->savepointLevel)
Will this ever be true in the current code? I cannot see anything setting
savepointLevel explicitly.
GavinIndex: src/backend/access/transam/xact.c
==
Bruce Momjian wrote:
Tom Lane wrote:
contrib/dbsize doesn't even compile, and I'm still of the opinion that
oid2name is going to be pretty useless if it doesn't know about
tablespaces.
Added to open items.
The patch I posted is now at
http://cvs.pgadmin.org/cgi-bin/viewcvs.cgi/pgadmin-tools/supp
On Mon, 2 Aug 2004, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > Oracle defines very few named exceptions. Instead, the intention is that
> > you define a name for a numeric exception and use it yourself.
>
> Yeah, I noticed that. It seems a spectacularly bad idea :-(. What
>
On Mon, 2004-08-02 at 22:37, Christopher Kings-Lynne wrote:
> Did this get through? Hadn't seen anyone comment on it, and I thought
> it was pretty major :P
>
I'd just like to second your claims. I have a snapshot from 2004-08-02
and I appended a sequence of SQL commands that causes a crash for
Hi Tom,
Thanks for your answer.
You mean I need to download another version and install it? If there is
anything to prevent a re-install, let me know it please.
The one installed and downloaded is the PostgreSQL 7.3.4 version of the
package. I have the following software installed (listing produ
On Tue, Aug 03, 2004 at 05:17:27PM +0800, Christopher Kings-Lynne wrote:
> >--
> >-- TOC entry 537 (OID 2663955)
> >-- Name: ~=; Type: OPERATOR; Schema: public; Owner: strk
> >-- Data Pos: 0
> >--
> >
> >CREATE OPERATOR ~= (
> >PROCEDURE = geometry_same,
> >LEFTARG = geometry,
> >RIGHTA
--
-- TOC entry 537 (OID 2663955)
-- Name: ~=; Type: OPERATOR; Schema: public; Owner: strk
-- Data Pos: 0
--
CREATE OPERATOR ~= (
PROCEDURE = geometry_same,
LEFTARG = geometry,
RIGHTARG = geometry,
COMMUTATOR = 2663954,
RESTRICT = eqsel,
JOIN = eqjoinsel
);
How about:
\x
SEL
Bruce Momjian wrote:
Jeff Davis wrote:
On Mon, 2004-08-02 at 12:35, Bruce Momjian wrote:
Does anyone have any more?
From reading the lists it seems like most of PITR is in. However, I
can't find any docs for it so I don't know how I'd test it. I downloaded
the latest snapshot and don't immediately
On Tue, Aug 03, 2004 at 04:49:48PM +0800, Christopher Kings-Lynne wrote:
> >Operator commutator is itself, and when reading the ascii version
> >of the dump (produced with -Fc) I see that this has been changed
> >with what was probably it's oid instead.
>
> Can you paste that ascii from the dump?
Operator commutator is itself, and when reading the ascii version
of the dump (produced with -Fc) I see that this has been changed
with what was probably it's oid instead.
Can you paste that ascii from the dump?
Is this a bug in pg_dump ?
How do I tell which pg_dump version produced the dump ?
I'm
Hi all,
when trying to restore a dump I get the following error:
pg_restore: [archiver (db)] could not execute query: ERROR: argument of commutator
must be a name
Operator commutator is itself, and when reading the ascii version
of the dump (produced with -Fc) I see that this has been changed
wi
68 matches
Mail list logo
