On Fri, 2002-11-29 at 18:06, Daniele Orlandi wrote:
- Better granularity of security and access control, like in mysql.
Can you be more specific on exactly what features you'd like to see?
- Ability to reset the state of an open backend, including aborting open
transaction to allow for
On Fri, 2002-11-29 at 23:32, Justin Clift wrote:
Vince Vielhaber wrote:
snip
Yes it would. But while on the subject, why did you only mention it's
availability being on the advocacy site?
*We* mentioned it's availability being on the Advocacy site, because it
gives people a single place
On Fri, 2002-11-29 at 13:51, Christopher Kings-Lynne wrote:
Just out of interest, if someone was going to pay you to hack on Postgres
for 6 months, what would you like to code for 7.4?
Here's some of my current TODO list:
* FOR EACH STATEMENT triggers (already done)
* column lists for UPDATE
What I'd like to have in future versions of PostgreSQL:
- replication, replication, ... (you have seen that before). i guess
most people would like to see that.
- a dblink like system for connecting to remote database systems
(not just PostgreSQL???)
something like CREATE REMOTE
Oops, there is something I have forgotten:
- nicing backends: this would be nice for administration tasks
- CREATE DATABASE ... WITH MAXSIZE (many providers would like to see
that; quotas are painful in this case - especially when porting the
database to a different or a second server)
My list is;
Point to Point and Broadcast replication
With point to point you specify multiple endpoints, with broadcast you can
specify a subnet address and the updates are broadcast over that subnet.
The difference being that point to point works well
And that's all ;)
Hannu Krosing
- and what will you do after January? ;-)
Just kidding. I hope you have a big fat bank account if you want to finish
all that!
--
Kaare Rasmussen--Linux, spil,--Tlf:3816 2582
Kaki Datatshirts,
Hi,
although I'm just a novice in this mailing list I'd like to give my
contribution to the 7.4 wishlist.
I'd like to add to the PostgreSQL code some new low-level, primitive
fuctions in order to give native support to FP-based algorithms for rule
mining (Frequent Pattern Growth and extensions
On Friday 29 November 2002 17:14, Joe Conway wrote:
[EMAIL PROTECTED] wrote:
Does anybody know if postgres support a SQL statement that handles two
diferent databases (in the same server)?
Have a look at the contrib/dblink directory in the standard postgresql
distro.
Didnt find such a
On Friday 29 November 2002 06:51 pm, Christopher Kings-Lynne wrote:
Hi guys,
Just out of interest, if someone was going to pay you to hack on Postgres
for 6 months, what would you like to code for 7.4?
My ones are:
* Compliant ADD COLUMN
* Integrated full text indexes
* pg_dump
Tom Lane wrote:
Mike Mascari [EMAIL PROTECTED] writes:
I curious if any of the rewriting of EXISTS and NOT EXISTS would
address the problem described by Date:
That should read I'm curious...
http://www.firstsql.com/iexist.htm
We are not here to redefine the SQL spec ... and especially
On Sat, 2002-11-30 at 01:40, Nicolai Tufar wrote:
And I happen to have bad luck to use PostgreSQL with Turkish locale. And, as
you
may know our I is not your I:
pgsql=# create table a(x char(1));
CREATE TABLE
pgsql=# grant SELECT ON a to PUBLIC;
ERROR: user public does
Someone know any ODBC driver without problem with UPPER CASE ?
--
Saludos Horacio Miranda.
[EMAIL PROTECTED]
PostgreSQL. Because life's too short to learn Oracle.:)
Billy
On Sat, 2002-11-30 at 07:57, Nicolai Tufar wrote:
With this, no matter what kind of I you used in names,
it is always going to end up a valid ASCII character.
Would it be acceptable if I submit a path that applies this
special logic in src/backend/parser/scan.l if the locale is tr_TR?
On Sat, 2002-11-30 at 05:55, Alvaro Herrera wrote:
On Fri, Nov 29, 2002 at 10:51:26AM -0800, Christopher Kings-Lynne wrote:
Just out of interest, if someone was going to pay you to hack on Postgres
for 6 months, what would you like to code for 7.4?
Well, nobody is paying me, but I want
On Fri, 2002-11-29 at 20:21, Christopher Kings-Lynne wrote:
Looks like the eWeek article has been published:
http://www.eweek.com/article2/0,3959,732789,00.asp
Sorry for sounding like such a dork :)
A very good article, imho, for psql: The one thing people will remember
about mysql: it
Nicolai Tufar [EMAIL PROTECTED] writes:
Historically programs that operate in Turkish locale have
chosen to hardcode the capitalisation of i in system
messages and identifier names like this:
Lower: I - i and Y' - i.
Upper: y' - I and i - I.
If that's the behavior you want, why don't you
Hans-Jürgen Schönig wrote:
What I'd like to have in future versions of PostgreSQL:
- PL/Sh should be in contrib. i know that the core team has decided
not to put it in the core but contrib would be fine (I keep forgetting
the URL of Peters website :( ...)
I like PL/Sh too, but too many
Neil Conway wrote:
On Fri, 2002-11-29 at 23:32, Justin Clift wrote:
Vince Vielhaber wrote:
snip
Yes it would. But while on the subject, why did you only mention it's
availability being on the advocacy site?
*We* mentioned it's availability being on the Advocacy site, because it
On Sat, 2002-11-30 at 16:13, Bruce Momjian wrote:
Hans-Jürgen Schönig wrote:
What I'd like to have in future versions of PostgreSQL:
- PL/Sh should be in contrib. i know that the core team has decided
not to put it in the core but contrib would be fine (I keep forgetting
the URL
Hannu Krosing wrote:
On Sat, 2002-11-30 at 16:13, Bruce Momjian wrote:
Hans-J?rgen Sch?nig wrote:
What I'd like to have in future versions of PostgreSQL:
- PL/Sh should be in contrib. i know that the core team has decided
not to put it in the core but contrib would be fine (I
Here is an updated version of our developers biography page. I am
interested in locations for:
Christopher Kings-Lynne
Barry Lind
Dave Page
Rod Taylor
The format is usually large city, state/province, country.
Also, I would like Company, Company URL for anyone
On Fri, 29 Nov 2002, Christopher Kings-Lynne wrote:
Just out of interest, if someone was going to pay you to hack on Postgres
for 6 months, what would you like to code for 7.4?
What would you guys do? Even if it isn't feasible right now...
Hmm, mine would probably be fixing foreign keys
http://odbc.postgresql.org/
Regards, Dave.
-Original Message-
From: Horacio Miranda [mailto:[EMAIL PROTECTED]]
Sent: 30 November 2002 14:54
To: [EMAIL PROTECTED]
Subject: [HACKERS] about ODBC
Someone know any ODBC driver without problem with UPPER CASE ?
--
Hi All,
here is my wishlist /very short/ :
* Oracle syntax support in OUTER JOIN
Thanks, Gabor
Hans-Jrgen Schnig wrote:
What I'd like to have in future versions of PostgreSQL:
- PL/Sh should be in contrib. i know that the core team has decided
not to put it in the core but
Me and Teodor hope to work on contrib/ltree to add support for sort of
xml. Any ideas are welcome !
Regards,
Oleg
On Fri, 29 Nov 2002, Christopher Kings-Lynne wrote:
Wow Hannu - your list puts mine to shame!
Application server support
* Compliant ADD COLUMN
I've missed the thread (if there was one), how is it non-compliant?
Thanks,
- Brandon
c: 917-697-8665h: 201-798-4983
b. palmer, [EMAIL PROTECTED]
On Sat, 2002-11-30 at 15:06, bpalmer wrote:
* Compliant ADD COLUMN
I've missed the thread (if there was one), how is it non-compliant?
ALTER TABLE .. ADD COLUMN colname integer DEFAULT 42 NOT NULL
CHECK(colname = 42) REFERENCES tab2 ON DELETE CASCADE;
Can't do the above in a single
On Wednesday, November 27, 2002, at 04:34 PM, David Walker wrote:
Does this mean that in the future '342' may not be valid as an insert
into a
numeric field and that we should be using 342 instead?
I didn't see an answer to this question, but I sincerely hope that the
answer is
no.
Can you see this tying in with my recent hack of contrib/ltree to work
with a wider range of node names?
On Sat, 30 Nov 2002, Oleg Bartunov wrote:
Me and Teodor hope to work on contrib/ltree to add support for sort of
xml. Any ideas are welcome !
---(end of
-Original Message-
From: David Wheeler [mailto:[EMAIL PROTECTED]]
Sent: 30 November 2002 20:18
To: David Walker
Cc: PostgreSQL Development
Subject: Re: [HACKERS] Boolean casting in 7.3 - changed?
On Wednesday, November 27, 2002, at 04:34 PM, David Walker wrote:
Does this
I didn't see an answer to this question, but I sincerely hope that the
answer is
no. Otherwise, dynamic interfaces are going to have a much harder
time.
Take DBI (and DBD::Pg), for example. Most DBI users don't specify a
data type when using placeholders. Therefore, DBD::Pg (and other
On Sat, 30 Nov 2002, Bruce Momjian wrote:
Neil Conway wrote:
On Fri, 2002-11-29 at 23:32, Justin Clift wrote:
Vince Vielhaber wrote:
snip
Yes it would. But while on the subject, why did you only mention it's
availability being on the advocacy site?
*We* mentioned it's
Darko Prenosil wrote:
Now when the 7.3 release is out,can we get back to plpq ?
I did send You sources before vacation, and You said that You will take a
look.
I hope I am not disturbing You. If You think that this is bad Idea, I give up
hope that we merge this functions into dblink, an I
- Original Message -
From: Hannu Krosing [EMAIL PROTECTED]
To: Nicolai Tufar [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, November 30, 2002 5:41 PM
Subject: Re: [HACKERS] Locale-dependent case conversion in {identifier}
[ ... ]
could it just be that we store
Christopher Kings-Lynne wrote:
Hi guys,
Just out of interest, if someone was going to pay you to hack on Postgres
for 6 months, what would you like to code for 7.4?
My ones are:
* Compliant ADD COLUMN
* Integrated full text indexes
* pg_dump dependency ordering
What would you guys do? Even
Ok, someone else posted their data warehousing wishlist, I want to post my
single item OLP wishlist: Plan stability. This is the natural conclusion of
having prepared queries.
This is one area where it would be possible to totally beat Oracle's
implementation by a huge margin. And it's something
On Saturday, November 30, 2002, at 01:44 PM, Joe Conway wrote:
* continue to improve usability of bytea datatype
- easier explicit casting between bytea and text
This wouldn't happen to include the idea of somehow eliminating the
difference between how text strings are delimited and how
I was thinking of hacking on postgres a bit. I want to start with filling out
the operations list for data types that seem to be missing obvious operators.
In particular I'm thinking of things like
. an aggregate function for cidr that would find the smallest enclosing netblock.
. an aggregate
This is weird, it seems like min and max aren't being optimised symmetrically.
It seems like both of these should result in similar plans and run equally
fast. Instead the first is actually really slow and the second is perfectly
quick.
foo=# explain select max(postalcode) from postalcodes
This is weird, it seems like min and max aren't being optimised
symmetrically.
It seems like both of these should result in similar plans and run equally
fast. Instead the first is actually really slow and the second is
perfectly
quick.
Without knowing anything about your data, if Postgres
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
This is weird, it seems like min and max aren't being optimised
symmetrically. It seems like both of these should result in similar plans
and run equally fast. Instead the first is actually really slow and the
second is perfectly quick.
Cross-db queries.
__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Is there any reason why the tseach indexes couldn't be modified to just work
on TEXT fields and not TXTIDX fields. Is there really a reason to have the
TXTIDX type?
I mean, when the index is created over the text column, instead of just
indexing the text as-is, index the txt2txtidx'd version...?
I'm seeing this:
I have indexed the suspended_off column.
usa=# explain analyze UPDATE users_users SET suspended=false,
suspended_on=NULL, suspended_off=NULL WHERE suspended_off='2002-02-02';
NOTICE: QUERY PLAN:
Index Scan using users_users_susp_off_idx on users_users
(cost=0.00..1005.91
Christopher Kings-Lynne wrote:
EXPLAIN
usa=# explain analyze UPDATE users_users SET suspended=false,
suspended_on=NULL, suspended_off=NULL WHERE suspended_off=CURRENT_DATE;
NOTICE: QUERY PLAN:
Seq Scan on users_users (cost=0.00..2927.26 rows=267 width=248) (actual
time=466.76..466.76 rows=0
On Saturday, November 30, 2002, at 04:14 PM, Joe Conway wrote:
Not quite sure what you mean by delimiter -- are you referring to
double
escaping vs single escaping?
Oh crap, yes, that's exactly what I meant.
s/delimited/escaped/g;
Sorry. :-)
David
--
David Wheeler
My ones are:
* Compliant ADD COLUMN
* Integrated full text indexes
* pg_dump dependency ordering
What would you guys do? Even if it isn't feasible right now...
Actually - I think I might add MODIFY COLUMN to that list. Just look at the
list of poor buggers in the interactive docs
src/bin/pg_dump/pg_dump.c happen to have hard-coded PUBLIC role name.
It completly breaks dumps when run with Turksh locale setting. In my
opinion making it lower-case would do much good and no harm. A mini
patch is given below.
On the other hand, I was thinking about wrapping all the identifiers
src/bin/pg_dump/pg_dump.c happen to have hard-coded PUBLIC role name.
It completly breaks dumps when run with Turksh locale setting. In my
opinion making it lower-case would do much good and no harm. A mini
patch is given below.
H...does putting double quotes (eg. PUBLIC) around the
We made SlashDot:
http://developers.slashdot.org/developers/02/11/30/1815200.shtml?tid=99
Greg - could you forward to advocacy?
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send
Is someone keeping a hopeful todo list?
- Brandon
c: 917-697-8665h: 201-798-4983
b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5
- Original Message -
From: Christopher Kings-Lynne [EMAIL PROTECTED]
To: Nicolai Tufar [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Sunday, December 01, 2002 4:05 AM
Subject: Re: [HACKERS] Hard-coded PUBLIC in pg_dump
H...does putting double quotes (eg. PUBLIC) around the public word
On Sat, 2002-11-30 at 21:22, bpalmer wrote:
Is someone keeping a hopeful todo list?
Nearly every one of the items brought up could / should be on the
standard todo list.
http://developer.postgresql.org/todo.php
--
Rod Taylor [EMAIL PROTECTED]
signature.asc
Description: This is a digitally
On Sat, 2002-11-30 at 12:47, Stephan Szabo wrote:
check constraints with subselects.
Have we decided how this would even work? Last I heard, Tom still had
some major reservations about the practicality of implementing these --
for example, would you re-evaluate all constraints that SELECT from a
David Wheeler wrote:
On Saturday, November 30, 2002, at 04:14 PM, Joe Conway wrote:
Not quite sure what you mean by delimiter -- are you referring to double
escaping vs single escaping?
Oh crap, yes, that's exactly what I meant.
s/delimited/escaped/g;
That is one thing I'd like to take a
Rod Taylor wrote:
-- Start of PGP signed section.
On Sat, 2002-11-30 at 21:22, bpalmer wrote:
Is someone keeping a hopeful todo list?
Nearly every one of the items brought up could / should be on the
standard todo list.
http://developer.postgresql.org/todo.php
Does anyone have additions
On Sat, 2002-11-30 at 23:02, Bruce Momjian wrote:
Rod Taylor wrote:
-- Start of PGP signed section.
On Sat, 2002-11-30 at 21:22, bpalmer wrote:
Is someone keeping a hopeful todo list?
Nearly every one of the items brought up could / should be on the
standard todo list.
Greg Stark [EMAIL PROTECTED] writes:
Ok, someone else posted their data warehousing wishlist, I want to post my
single item OLP wishlist: Plan stability.
That seems to me to translate to I want the system to fail to react to
changes in data statistics and all other variables relevant to query
We recently finished some evaluations of Oracle, and one of the things
which jumped out at me, PostgreSQL booster that I am, was that in 9i
Oracle has finally surpassed PostgreSQL in some elements of
object-relational technology. Among the things you can do are:
- Create new compound object types
Nicolai Tufar [EMAIL PROTECTED] writes:
src/bin/pg_dump/pg_dump.c happen to have hard-coded PUBLIC role name.
As it should. I think the real problem here is the hack in gram.y:
grantee:ColId
{
PrivGrantee *n = makeNode(PrivGrantee);
Paul Ramsey [EMAIL PROTECTED] writes:
Oracle has finally surpassed PostgreSQL in some elements of
object-relational technology. Among the things you can do are:
- Address components of objects using dot-notation. (select
employee.salary from employees)
Cool. How do they resolve the conflict
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Why does using CURRENT_DATE instead of a literal date make a difference?
In 7.3 it doesn't. Prior versions do not understand that CURRENT_DATE
can be treated like a constant in this context. Time to update ;-)
regards,
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
... but considering that SQL92 clearly lists it as
a reserved word, there's not a lot of ground for that complaint to stand
on.
I'd prefer shifting PUBLIC back to the true-keyword category over any
of the other workarounds
Someone asked earlier about how to change a bunch of existing tables int the
PUBLIC schema to some other schema. For grins I tried:
regression=# select oid,* from pg_namespace ;
oid | nspname | nspowner | nspacl
++--+
11 | pg_catalog |1 |
Joe Conway [EMAIL PROTECTED] writes:
Someone asked earlier about how to change a bunch of existing tables int the
PUBLIC schema to some other schema. For grins I tried:
regression=# update pg_class set relnamespace=556829 where relname = 'foo' and
relnamespace=2200;
UPDATE 1
and it seemed
Joe Conway [EMAIL PROTECTED] writes:
- possibly enhanced connectby functionality (may not be worth it if
RECURSIVE JOIN functionality makes it into 7.4)
Several of my Red Hat cohorts are pretty interested in making the
RECURSIVE query stuff work for 7.4. (The fact that they're ex-DB2
Tom Lane wrote:
Joe Conway [EMAIL PROTECTED] writes:
Someone asked earlier about how to change a bunch of existing tables int the
PUBLIC schema to some other schema. For grins I tried:
regression=# update pg_class set relnamespace=556829 where relname = 'foo' and
relnamespace=2200;
UPDATE 1
I've spent today messing with making the planner substitute inline
definitions of simple SQL functions, per the comment in
src/backend/optimizer/util/clauses.c:
* XXX Possible future improvement: if the func is SQL-language, and its
* definition is simply SELECT expression, we could parse and
Tom Lane wrote:
It seems to work 99%, but I'm seeing this failure in the regression
tests:
CREATE FUNCTION getfoo(int) RETURNS int AS 'SELECT $1;' LANGUAGE SQL;
SELECT * FROM getfoo(1) AS t1;
! ERROR: ExecMakeTableFunctionResult: expression is not a function call
which of course happens
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
Ohhh ...
Nicolai, are you running with a client encoding different from server
encoding?
Got it!
Gentlemen, thank you very much for assistance. The body of evidence was
slowly
growing, then, finaly Tom Lan's message have
71 matches
Mail list logo
