Hi all,
Does anyone else have an opinion on this? If not, I will implement it per
Bruce's commentary.
Gavin
On Mon, 2 Sep 2002, Bruce Momjian wrote:
Gavin Sherry wrote:
Okay, my bad. From my reading of the email exchange, I thought people
wanted this on -- always. The best solution for
Yes, I would like to know if it should be enabled by default, and
whether we need a way to turn it off. I assume, considering the size of
some of the queries, that we have to have a way to turn it off, and it
is possible the admin may not want queries in the log, even if the
generate errors.
OK, the HISTORY file is updated, and 7.3 is branded and ready for beta1.
I used the same HISTORY categories Peter made in 7.2. I liked them.
Please review the HISTORY file. I am sure there are improvements that
can be made.
--
Bruce Momjian|
On 4 Sep 2002 at 3:24, Bruce Momjian wrote:
OK, the HISTORY file is updated, and 7.3 is branded and ready for beta1.
I used the same HISTORY categories Peter made in 7.2. I liked them.
Please review the HISTORY file. I am sure there are improvements that
can be made.
Some minor stuff,
I assume you are not looking at the 7.3 release notes. It does take a
while for anon to get the changes.
---
Shridhar Daithankar wrote:
On 4 Sep 2002 at 3:24, Bruce Momjian wrote:
OK, the HISTORY file is updated,
Hello everyone.
I can't understand Tid Scan, Who can tell me what it's that and where I could find
document on the Web. Thanks for your reponse.
Guo longjiang Harbin China
__
===
Hello, Mr. Tom Lane
I am a chinese student studied in Harbin institute of technology. I want join to
PostgreSQL Global Development Group and I want work on the planner/optimizer. I have
been reading the source code for 2 months. There many data strucutres I can't
understand. Can you tell me
OK, the HISTORY file is updated, and 7.3 is branded and ready for beta1.
I used the same HISTORY categories Peter made in 7.2. I liked them.
Please review the HISTORY file. I am sure there are improvements that
can be made.
Please change:
Add CREATE/DROP CONVERSION, allowing loadable
I found one bug in file src/backend/utils/adt/oracle_compat.c and there were
your name, related with Multibyte enhancement, so i write to you.
Functions upper,lower and initcap doesn't work with utf-8 data which is not of
Latin letters.At my work i do databases for Russian users and
Found this line without a name:
Propagate column or table renaming to foreign key constraints
Is that item complete? pg_constraint follows (as such dump / restore
will work) but the triggers themselves still break, don't they?
On Wed, 2002-09-04 at 03:24, Bruce Momjian wrote:
OK, the HISTORY
On Wed, 2002-09-04 at 12:43, ljguo_1234 wrote:
Hello everyone.
I can't understand Tid Scan, Who can tell me what it's that and where I could
find document on the Web. Thanks for your reponse.
It is scanning table by TupleID's. A tuple id is a 6-byte entity which
consists of 4-byte page
Warning: Supplied argument is not a valid PostgreSQL link resource in
/usr/local/www/gborg3/html/index.php on line 52
Warning: Supplied argument is not a valid PostgreSQL link resource in
/usr/local/www/gborg3/html/include/project.php on line 196
Warning: Supplied argument is not a valid
On Wed, 4 Sep 2002, Christopher Kings-Lynne wrote:
Warning: Supplied argument is not a valid PostgreSQL link resource in
/usr/local/www/gborg3/html/index.php on line 52
Looks like the machine with the database on it. The mirror update
cronjob is failing too.
Vince.
--
Can anyone find an email in all of that? I did a search of 'afk' ... oops
:) got it and removed ...
On Wed, 4 Sep 2002, Christopher Kings-Lynne wrote:
Does anyone else get this rubbish when they post to -php ?
Our domain isn't on any blacklists AFAIK...
Chris
-Original
Gavin Sherry [EMAIL PROTECTED] writes:
Does anyone else have an opinion on this? If not, I will implement it per
Bruce's commentary.
On Mon, 2 Sep 2002, Bruce Momjian wrote:
I think the second, passing an arg to say whether it is server or
client, will do the trick, though now you need an
Bruce Momjian [EMAIL PROTECTED] writes:
Yes, I would like to know if it should be enabled by default, and
whether we need a way to turn it off.
I feel it should be off by default --- if enough people say hey, this
is great then maybe we could turn it on by default, but we don't yet
have that
Rod Taylor [EMAIL PROTECTED] writes:
Found this line without a name:
Propagate column or table renaming to foreign key constraints
Is that item complete? pg_constraint follows (as such dump / restore
will work) but the triggers themselves still break, don't they?
Yes, no. There's hackery
should already be fixed ...
On Wed, 4 Sep 2002, Vince Vielhaber wrote:
On Wed, 4 Sep 2002, Christopher Kings-Lynne wrote:
Warning: Supplied argument is not a valid PostgreSQL link resource in
/usr/local/www/gborg3/html/index.php on line 52
Looks like the machine with the database on
On Wed, 4 Sep 2002, Christopher Kings-Lynne wrote:
Cool. Is it worth putting it on greatbridge? gborg.postgresql.org
greatbridge is back again? *raised eyebrow*
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Shridhar Daithankar dijo:
On 4 Sep 2002 at 3:24, Bruce Momjian wrote:
OK, the HISTORY file is updated, and 7.3 is branded and ready for beta1.
Some minor stuff,
In the schema changes description:
Schemas allow users to create objects in their own namespace
so two people can have the
Joe Conway [EMAIL PROTECTED] writes:
I'm not sure I interpreted the intent of findoidjoins just right, but
here it is updated for schemas, new reg* types, using SPI instead of
libpgeasy, and returning the results as a table function. Any
corrections/comments?
For what we want it for (viz,
On Fri, Aug 30, 2002 at 02:43:38PM -0400, Matthew T. OConnor wrote:
As someone else mentioned (I think), even using a separate schema is not
always an acceptable option. If you are using a packaged application
(whether commercial or open source), you usually don't want *any*
changes to
Hi,
I think I figured why I can't buil plperl on unixware 711/OpenUnix 800.
It seems Makefile.shlib has changed between 722 and 73 and -z text has
been added. However with this on, it fails to build libperl.so
Maybe I'm wrong, but could someone consider this patch.
Regards,
--
Olivier
Shridhar Daithankar dijo:
On 4 Sep 2002 at 3:24, Bruce Momjian wrote:
OK, the HISTORY file is updated, and 7.3 is branded and ready for beta1.
Some minor stuff,
In the schema changes description:
Schemas allow users to create objects in their own namespace
so two people
Tom Lane wrote:
For what we want it for (viz, regenerating the oidjoins test every so
often), this is really a step backwards. It requires more work to run
than the original program, and it modifies the database under test,
which is undesirable because it's commonly run against template1.
Ross wrote:
I'm a bit late on this discussion, but I, for one, have liked
having
some of the pgaccess info stored with the database. That way,
no matter
what machine I connect to the DB from, I get the same set of
functions,
queries, and schema-documents.
Very much true.
A wiki page
Joe Conway [EMAIL PROTECTED] writes:
Is it useful to have the reference count and unreferenced counts like
currently written, or should I just faithfully reproduce the original
behavior (except schema aware queries) using libpq in place of libpgeasy?
I'd be inclined to reproduce the
Tom Lane wrote:
Joe Conway [EMAIL PROTECTED] writes:
Is it useful to have the reference count and unreferenced counts like
currently written, or should I just faithfully reproduce the original
behavior (except schema aware queries) using libpq in place of libpgeasy?
I'd be inclined to
- Original Message -
From: Olivier PRENANT [EMAIL PROTECTED]
Sent: September 04, 2002 12:18 PM
I think I figured why I can't buil plperl on unixware 711/OpenUnix 800.
It seems Makefile.shlib has changed between 722 and 73 and -z text has
been added. However with this on, it fails
Peter Eisentraut [EMAIL PROTECTED] writes:
I found an HP whitepaper on the large file support and it seems they don't
have the problem of missing declarations.
http://docs.hp.com/hpux/onlinedocs/os/lgfiles4.pdf
Note the example in section 6.4.1. On page 37 they grep the preprocessed
source
Patch withdrawn by author.
---
Joe Conway wrote:
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Christopher Kings-Lynne dijo:
findoidjoins doens't seem to compile:
Seems related to the ripping of libpgeasy
Oops...
This one should be all right!!
Sorry
Regards
On Wed, 4 Sep 2002, Serguei Mokhov wrote:
Date: Wed, 4 Sep 2002 12:23:11 -0400
From: Serguei Mokhov [EMAIL PROTECTED]
To: [EMAIL PROTECTED], pgsql-hackers list [EMAIL PROTECTED]
Subject: Re: [HACKERS] Bug in Makefile.shlib
-
Tatsuo Ishii wrote:
OK, the HISTORY file is updated, and 7.3 is branded and ready for beta1.
I used the same HISTORY categories Peter made in 7.2. I liked them.
Please review the HISTORY file. I am sure there are improvements that
can be made.
Please change:
Add CREATE/DROP
Hot sure if this is the right list, but. . .
On Mon, Sep 02, 2002 at 08:20:14PM -0400, Vince Vielhaber wrote:
On Sat, 31 Aug 2002, Marc G. Fournier wrote:
This is all in Vince's area ...
Correction. You're not looking, it's in the users lounge. We've
covered the button thing
I assume you have read everything on the developers web page:
http://developer.postgresql.org/index.php
---
ljguo_1234 wrote:
Hello, Mr. Tom Lane
I am a chinese student studied in Harbin institute of
Rod Taylor wrote:
Found this line without a name:
Propagate column or table renaming to foreign key constraints
Is that item complete? pg_constraint follows (as such dump / restore
will work) but the triggers themselves still break, don't they?
No idea. The item only talks about the
Hi,
Under what conditions would the following statement cause the USERS
table to lock out selects?
alter table my_coupons
add constraint FK_mc_user_id
FOREIGN KEY (mc_frn_user_id)
REFERENCES users(user_ID);
ss
Scott Shattuck
Technical Pursuit Inc.
---(end
Alvaro Herrera wrote:
Shridhar Daithankar dijo:
On 4 Sep 2002 at 3:24, Bruce Momjian wrote:
OK, the HISTORY file is updated, and 7.3 is branded and ready for beta1.
Some minor stuff,
In the schema changes description:
Schemas allow users to create objects in their own
On 4 Sep 2002, Scott Shattuck wrote:
Under what conditions would the following statement cause the USERS
table to lock out selects?
alter table my_coupons
add constraint FK_mc_user_id
FOREIGN KEY (mc_frn_user_id)
REFERENCES users(user_ID);
If I'm reading code correctly, an
OK, wording updated to add 'applications':
Schemas allow users to create objects in their own namespace
so two people or applications can have tables with the same
name. There is also a public schema for shared tables.
Table/index creation can be
OK, I talked to Marc and he is going to package up beta1 tonight.
Any more changes to HISTORY?
I want to run pgindent in an hour. Does anyone have a problem with
that?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+
Bruce Momjian wrote:
OK, the HISTORY file is updated, and 7.3 is branded and ready for beta1.
I used the same HISTORY categories Peter made in 7.2. I liked them.
Please review the HISTORY file. I am sure there are improvements that
can be made.
A few minor comments:
1. suggested
Joe Conway wrote:
Bruce Momjian wrote:
OK, the HISTORY file is updated, and 7.3 is branded and ready for beta1.
I used the same HISTORY categories Peter made in 7.2. I liked them.
Please review the HISTORY file. I am sure there are improvements that
can be made.
A few minor
Olivier PRENANT [EMAIL PROTECTED] writes:
I think I figured why I can't buil plperl on unixware 711/OpenUnix 800.
It seems Makefile.shlib has changed between 722 and 73 and -z text has
been added.
Not hardly. The -z text option has been in there since at least 6.4.
6.4's Makefile.shlib has
On Wed, 2002-09-04 at 12:28, Tom Lane wrote:
Olivier PRENANT [EMAIL PROTECTED] writes:
I think I figured why I can't buil plperl on unixware 711/OpenUnix 800.
It seems Makefile.shlib has changed between 722 and 73 and -z text has
been added.
Not hardly. The -z text option has been in
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Please review the HISTORY file.
PostgreSQL now support ALTER TABLE ... DROP COLUMN functionality.
s/support/supports/
Functions can now return sets, with multiple rows
and multiple columns. You
Bruce Momjian [EMAIL PROTECTED] writes:
I don't remember every seeing a function returning sets before. Can you
give an example?
http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/xfunc-sql.html#AEN26392
Also, the preceding subsection shows SQL functions returning rows. So
these
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I don't remember every seeing a function returning sets before. Can you
give an example?
http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/xfunc-sql.html#AEN26392
Also, the preceding subsection shows SQL functions
will announce it on -announce tomorrow, if ppl want to take a quick look
at it ... man pages weren't included, but I did regenerate the docs per
Peter's suggested commands ...
Scary, even with removing a load of stuff over to gborg, its still gotten
bigger then the last release :)
%ls -lt
Bruce Momjian [EMAIL PROTECTED] writes:
Yes, now I remember, only SQL functions could return sets. How about
this:
PL/PgSQL and C functions can now return sets, with multiple
rows and multiple columns. You specify these functions in the
SELECT FROM clause,
Tom Lane wrote:
C functions have always been able to return sets too; you don't honestly
think that a SQL function can do something a C function can't, do you?
The original dblink is an example.
There are really two independent improvements here: one is the ability
for plpgsql functions
Joe Conway wrote:
What about this:
Functions returning multiple rows and/or multiple columns are
now much easier to use than before. You can call such a
table function in the SELECT FROM clause, treating its output
like a table. Also, plpgsql functions can now return sets.
Added.
--
Well, Tom and Larry,
I've posted already on -hackers but my posts did'nt semm to get through!
The problem is that at link time, ld complains about text segment beeing
written to in Dynaloader.
The only way was to remove -Wl,-z text.
I agree this sounded stupid. But I can't think of something
Me again!!
These are errors I get with orginal Makefile.shlib:
Warning: No bytecode-native mapping for a bytecode
Warning: JIT compiler failed for org/apache/crimson/parser/Parser2.maybeComment(Z)Z
UX:ld: INFO: text relocations referenced from files:
DynaLoader.a(DynaLoader.o)
UX:ld: ERROR:
Olivier PRENANT [EMAIL PROTECTED] writes:
The problem is that at link time, ld complains about text segment beeing
written to in Dynaloader.
I agree this sounded stupid. But I can't think of something else.
This is with perl-5.6.1 FWIW
Ah. This is a bug in Perl's build process: even if you
Hi Tom,
Thanks fr your reply.. Not sure I understood!
I've tried your hack with no luck. Further more, README in
perl/ext/Dynaloader says it has to be static to be effective.
What concerns me more is that with same perl (5.6.1) it compiles ok with
722.
Regards
On Wed, 4 Sep 2002, Tom Lane
Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Now that the multibyte-based character set recoding is a fixed part of
the feature set, is there any need to keep the Cyrillic recode support?
It's probably not worth maintaining anymore ...
Added to TODO:
* Remove
Olivier PRENANT [EMAIL PROTECTED] writes:
Thanks fr your reply.. Not sure I understood!
I've tried your hack with no luck. Further more, README in
perl/ext/Dynaloader says it has to be static to be effective.
That's talking about whether it's linked into perl, not whether it's
compiled PIC or
Bruce Momjian [EMAIL PROTECTED] writes:
Any more changes to HISTORY?
This is missing:
- Implemented START TRANSACTION, per SQL99 (Neil)
This was implemented by Peter, I think:
- Add privileges on functions and procedural languages
This was done by Tom, IIRC:
- Triggers are now fired in
Tatsuo Ishii writes:
Functions upper,lower and initcap doesn't work with utf-8 data
The backend routines use the host OS locales, so look there. On my
machine I have several Russian locales, which seem to address the issue of
character sets:
ru_RU
ru_RU.koi8r
ru_RU.utf8
ru_UA
russian
I just tried to build all of contrib, and it stops at earthdistance.
Looks like this is the cause:
[...]
dbmirror\
dbsize \
earthdistance \
# findoidjoins\
fulltextindex \
[...]
The comment
I'm also getting a failure on tsearch:
make[1]: Entering directory `/opt/src/pgsql/contrib/tsearch'
gcc -O2 -g -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I.
-I../../src/include -c -o morph.o morph.c -MMD
morph.c: In function `initmorph':
morph.c:107: `PG_LocaleCategories'
Here are a few open concerns about pg_dump:
Critical:
* pg_dumpall is not compatible with pre-7.3. It used to be ignorant but
now that it has extra columns in pg_database and pg_user to take care of
it will break with older releases. This should be straightforward to fix
for me (I hope)
Larry Rosenman [EMAIL PROTECTED] writes:
I upgraded PostgreSQL to 7.2.1 from a 7.2beta (yeah, I know). One of my
users requested plperl, so I got it to createlang, but it SIGSEGV's on
any simple perl.
I was seeing the same with perl 5.6.1 and PG 7.2.* on HPUX 10.20.
However, I have just
On Thu, 5 Sep 2002, Peter Eisentraut wrote:
Date: Thu, 5 Sep 2002 00:46:39 +0200 (CEST)
From: Peter Eisentraut [EMAIL PROTECTED]
To: Tatsuo Ishii [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [HACKERS] Multibyte support in oracle_compat.c
Tatsuo Ishii writes:
Hannu Krosing wrote:
On Thu, 2002-09-05 at 03:17, Neil Conway wrote:
Tom did some work on this as well as Chris, I believe:
- Add ALTER TABLE DROP COLUMN (Christopher)
IIRC, some of it was originally based on Hiroshi's earlyer trial code,
so he should probably be mentioned as well
Neil Conway wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Any more changes to HISTORY?
This is missing:
- Implemented START TRANSACTION, per SQL99 (Neil)
Done. I didn't mention it earlier because I was unsure of its
significance.
This was implemented by Peter, I think:
- Add
On Wed, 2002-09-04 at 15:51, Stephan Szabo wrote:
On 4 Sep 2002, Scott Shattuck wrote:
Under what conditions would the following statement cause the USERS
table to lock out selects?
alter table my_coupons
add constraint FK_mc_user_id
FOREIGN KEY (mc_frn_user_id)
Scott Shattuck [EMAIL PROTECTED] writes:
... I don't understand why an exclusive table-level lock is being
taken out to add a trigger.
Well, that's a schema change; it makes sense to me to forbid access
while we're changing a table's schema.
I think this discussion may just be a
A long time ago you mentioned in passing that postgres.h should be
included before including any system headers. I have been desultorily
changing files to meet that rule, but AFAIK no one's made a pass to
ensure that it's followed everywhere.
Well, now we have a reason it had better be that
On Wed, 2002-09-04 at 17:54, Tom Lane wrote:
Larry Rosenman [EMAIL PROTECTED] writes:
I upgraded PostgreSQL to 7.2.1 from a 7.2beta (yeah, I know). One of my
users requested plperl, so I got it to createlang, but it SIGSEGV's on
any simple perl.
I was seeing the same with perl 5.6.1
Peter Eisentraut [EMAIL PROTECTED] writes:
I was wondering why we
don't do this:
BEGIN;
UPDATE ...
COPY ...
UPDATE ...
COMMIT;
Seems like a good idea.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill
The backend routines use the host OS locales, so look there. On my
machine I have several Russian locales, which seem to address the issue of
character sets:
ru_RU
ru_RU.koi8r
ru_RU.utf8
ru_UA
russian
This is bogus, because the LC_CTYPE choice is cluster-wide and the
encoding
On Tue, 3 Sep 2002, Bruce Momjian wrote:
Yep, this is where we are stuck; having an index span multiple tables
in some way.
Or implementing it by keeping all data in the table in which it
was declared. (I.e., supertable holds all rows; subtable holds
only the primary key and those columns of
Can someone maybe do a bit of a 'wc' on the cvs logs to see how much we've
changed between 7.2 - 7.3 compared to 7.1 - 7.2? It's evident that the
HISTORY file shows many more changes in this release than the previous, and
I think it'd be interesting to know how much/how fast postgres is gaining
Hannu Krosing wrote:
On Thu, 2002-09-05 at 03:17, Neil Conway wrote:
Tom did some work on this as well as Chris, I believe:
- Add ALTER TABLE DROP COLUMN (Christopher)
IIRC, some of it was originally based on Hiroshi's earlyer trial code,
so he should probably be mentioned as
It would be far simpler to put each of the core teams names on the top
of the history file in big bold letters -- or perhaps a watermark in the
background ;)
While we're competing for the humble award, you might want to add Tom to
that list...
---(end of
Oleg knows about it and is planning to fix it.
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Joe Conway
Sent: Thursday, 5 September 2002 11:55 AM
To: pgsql-hackers
Subject: [HACKERS] more contrib breakage
I'm also getting a failure on
Christopher Kings-Lynne wrote:
Hannu Krosing wrote:
On Thu, 2002-09-05 at 03:17, Neil Conway wrote:
Tom did some work on this as well as Chris, I believe:
- Add ALTER TABLE DROP COLUMN (Christopher)
IIRC, some of it was originally based on Hiroshi's earlyer trial code,
Is this item completed? It sure looks like it:
* Make triggers refer to columns by number, not name
test= \d pg_trigger
Table pg_catalog.pg_trigger
Column |Type| Modifiers
++---
tgrelid| oid| not null
tgname
On 4 Sep 2002, Scott Shattuck wrote:
On Wed, 2002-09-04 at 15:51, Stephan Szabo wrote:
On 4 Sep 2002, Scott Shattuck wrote:
Under what conditions would the following statement cause the USERS
table to lock out selects?
alter table my_coupons
add constraint
On Wed, 2002-09-04 at 22:49, Tom Lane wrote:
Scott Shattuck [EMAIL PROTECTED] writes:
... I don't understand why an exclusive table-level lock is being
taken out to add a trigger.
Well, that's a schema change; it makes sense to me to forbid access
while we're changing a table's schema.
Hang on - try looking at the tgargs field. I bet it still refers to fields
by their name, not their number...
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Bruce Momjian
- CVS
Sent: Thursday, 5 September 2002 12:58 PM
To: [EMAIL
Anyone else think we should add some more pins to the developer map? At the
moment, it looks like we have very few developers!
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send
Yep, I see in regression database:
tgargs
---
clstr_tst_con\000clstr_tst\000clstr_tst_s\000UNSPECIFIED\000b\000rf_a\000
I will work on that this month. It is part of the advocacy project.
---
Christopher Kings-Lynne wrote:
Anyone else think we should add some more pins to the developer map? At the
moment, it looks like we have very few
Christopher Kings-Lynne wrote:
Can someone maybe do a bit of a 'wc' on the cvs logs to see how much we've
changed between 7.2 - 7.3 compared to 7.1 - 7.2? It's evident that the
HISTORY file shows many more changes in this release than the previous, and
I think it'd be interesting to know how
Line 72 of the HISTORY file (the one in 7.3b1 that Marc just packaged) reads:
* Pre-6.3 clients are no longer supported.
Is that supposed to be 7.3? I assume you're referring to the catalog changes,
c. that make old clients that are dependent on them behave incorrectly.
Regards,
Jeff
* Pre-6.3 clients are no longer supported.
Is that supposed to be 7.3? I assume you're referring to the
catalog changes,
c. that make old clients that are dependent on them behave incorrectly.
Regards,
Jeff Davis
No, he's referring to the on-the-wire protocol. This means that the
89 matches
Mail list logo
