7.2 items

Bruce Momjian wrote:

* Add replication of distributed databases [replication]
o automatic fallover

Shouldn't that be 'failover'? I don't know if I want automatic 'fallover'!

:-)
Andrew.
--
_____________________________________________________________________
Andrew McMillan, e-mail: Andrew@catalyst.net.nz
Catalyst IT Ltd, PO Box 10-225, Level 22, 105 The Terrace, Wellington
Me: +64(21)635-694, Fax: +64(4)499-5596, Office: +64(4)499-2267xtn709

Bruce Momjian wrote:

* Add replication of distributed databases [replication]
o automatic fallover

Shouldn't that be 'failover'? I don't know if I want automatic 'fallover'!

Just one letter, but a huge difference. :-)

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

I'm not sure about this one, but it should be possible to change the type of
a column without vacuum, to reoorder the columns, change the name,...

It would allow people who design GUIs to PG to do a very nice designer
interface (like on MS SQL7.0).

Also on the design part, the UML standard and others allow the drawing of
interfaces (ArgoUML, Dia,..). Someone could work out an export from UML
graph to PG Table Creation.

I'm still working on a new geographic type (geoobj) for PG follwing ISO
standards. Except the standard is still a draft. So I can't meet any
deadline... (fmaps.sourceforge.net)

Franck Martin
Network and Database Development Officer
SOPAC South Pacific Applied Geoscience Commission
Fiji
E-mail: franck@sopac.org <mailto:franck@sopac.org>
Web site: http://www.sopac.org/ <http://www.sopac.org/&gt;
Support FMaps: http://fmaps.sourceforge.net/ <http://fmaps.sourceforge.net/&gt;

This e-mail is intended for its addresses only. Do not forward this e-mail
without approval. The views expressed in this e-mail may not be necessarily
the views of SOPAC.

-----Original Message-----
From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
Sent: Friday, 11 May 2001 5:21
To: PostgreSQL-development
Subject: [HACKERS] 7.2 items

Here is a small list of big TODO items. I was wondering which ones
people were thinking about for 7.2?

---------------------------------------------------------------------------

* Add replication of distributed databases [replication]
o automatic fallover
o load balancing
o master/slave replication
o multi-master replication
o partition data across servers
o sample implementation in contrib/rserv
o queries across databases or servers (two-phase commit)
* Point-in-time data recovery using backup and write-ahead log
* Allow row re-use without vacuum (Vadim)
* Add the concept of dataspaces/tablespaces [tablespaces]
* Allow better control over user privileges [privileges]
* Allow elog() to return error codes, module name, file name, line
number, not just messages [elog]
* Allow international error message support and add error codes [elog]
* Make binary/file in/out interface for TOAST columns
* Large object interface improvements
* Allow inherited tables to inherit index, UNIQUE constraint, and primary
key
[inheritance]
* Add ALTER TABLE DROP COLUMN feature [drop]
* Add ALTER TABLE ... DROP CONSTRAINT
* Automatically drop constraints/functions when object is dropped

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

Here is a small list of big TODO items. I was wondering which ones
people were thinking about for 7.2?

The need for stored procedures that return a record set.
This is required to migrate from MSSQL, Interbase and others.
This is a commonly requested item.

Nested Transactions. This allows the logging of the execution of a failed
SQL
statement even if the rest of the transaction is rolled back.

Statement Level Triggers. Useful but not critically important.

Full text indexing.

Pre parsed queries with variable substitutions.

Regards

Bruce Momjian <pgman@candle.pha.pa.us> writes:

Here is a small list of big TODO items. I was wondering which ones
people were thinking about for 7.2?

Peter E. had implied that he wanted to tackle the elog issues for 7.2,
but I'm not sure if he's committed to it or not.

I am wanting to see SQL schemas happen, and it's possible that
tablespaces should be dealt with in combination with that.

Other than that, I'm mostly thinking about performance improvements
for 7.2, not features ... as far as my personal plans go, that is.

regards, tom lane

* Point-in-time data recovery using backup and write-ahead

log > * Allow row re-use without vacuum (Vadim)

Yhis one is not very important for my, but I guess there are
people out there that have heavy updates on there DB and would
be delighted with this.

Yes, this important especially for databases that have to be up 24
hours a day.

* Add the concept of dataspaces/tablespaces [tablespaces]

What would this be?

What I'm about to write has nothing (at least I think) to do
with this, but I would like the database directoies to have the
name of the databases, as it was before, if it's posible. It
makes it easier to find out with database is growing from the
command line.

We have a /contrib utility called oid2name for that.

* Allow better control over user privileges [privileges]

If this is related with the views and privileges, I'm on this
one!

Not sure what the problem is there. We already implement privileges on
views that are separate from the base tables.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Full text indexing.

This one is already done using GIST. The GIST improvements are in 7.1,
and I assume full text indexing will be more fully integrated into
PostgreSQL in 7.2.

The PostgreSQL web search engine is using it now. Oleg and team did the
work.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Bruce Momjian <pgman@candle.pha.pa.us> writes:

Here is a small list of big TODO items. I was wondering which ones
people were thinking about for 7.2?

Peter E. had implied that he wanted to tackle the elog issues for 7.2,
but I'm not sure if he's committed to it or not.

I put Peter E on that one with a question mark.

I am wanting to see SQL schemas happen, and it's possible that
tablespaces should be dealt with in combination with that.

Updated TODO.

Other than that, I'm mostly thinking about performance improvements
for 7.2, not features ... as far as my personal plans go, that is.

Seems you already started.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Other than that, I'm mostly thinking about performance improvements
for 7.2, not features ... as far as my personal plans go, that is.

I saw a few juicy TODO items I will tackle, though people will
certainly be cleaning up after me. :-)

I have reorganized the TODO list to make smaller groupings.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

* Bruce Momjian <pgman@candle.pha.pa.us> [010510 17:02] wrote:

* Point-in-time data recovery using backup and write-ahead

log > * Allow row re-use without vacuum (Vadim)

Yhis one is not very important for my, but I guess there are
people out there that have heavy updates on there DB and would
be delighted with this.

Yes, this important especially for databases that have to be up 24
hours a day.

Sorry for jumping in here, but any ideas on the expected date
that will become available?

--
-Alfred Perlstein - [alfred@freebsd.org]
Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.

* Add ALTER TABLE ... DROP CONSTRAINT

I am working on this function at the moment, hoping to add the dropping of
CHECK constraints. However, it'll take me a while because I keep having to
look up all the functions being called to see what they do, etc.

What I'm thinking it that I'll try and at least get the structure all done
and even compiling then the patch will have to be reviewed. (I'm doing it to
stretch my programming muscles after working in PHP for so long!)

Chris

* Add ALTER TABLE ... DROP CONSTRAINT

I am working on this function at the moment, hoping to add the dropping of
CHECK constraints. However, it'll take me a while because I keep having to
look up all the functions being called to see what they do, etc.

What I'm thinking it that I'll try and at least get the structure all done
and even compiling then the patch will have to be reviewed. (I'm doing it to
stretch my programming muscles after working in PHP for so long!)

Good idea. Certain people are great at looking at a patch and telling
exactly how to improve it.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

At 01:20 PM 10-05-2001 -0400, Bruce Momjian wrote:

* Allow row re-use without vacuum (Vadim)

Will this do away with the need for a lazy vacuum?

Full text indexing.

This one is already done using GIST. The GIST improvements are in 7.1,
and I assume full text indexing will be more fully integrated into
PostgreSQL in 7.2.

I hope it will. What will the interface be like?

Right now I still don't know how to do FTI in 7.1 using _postgresql_ built
in GIST :(.

Any pointers to the relevant postgresql docs?

Cheerio,
Link.

Quoting Bruce Momjian <pgman@candle.pha.pa.us>:

* Point-in-time data recovery using backup and write-ahead

log > * Allow row re-use without vacuum (Vadim)

Yhis one is not very important for my, but I guess there are
people out there that have heavy updates on there DB and would
be delighted with this.

Yes, this important especially for databases that have to be up 24
hours a day.

I always thought that VACUUM was (especially) for 2 main reasons there:
- Clean de tuples marked for deletion.
- Make the new statistics. (-z)

Lots of tuples get marked for deletion on UPDATE and DELETE, am I right?

* Add the concept of dataspaces/tablespaces [tablespaces]

What would this be?

What I'm about to write has nothing (at least I think) to do
with this, but I would like the database directoies to have the
name of the databases, as it was before, if it's posible. It
makes it easier to find out with database is growing from the
command line.

We have a /contrib utility called oid2name for that.

I'll check that. :-)

* Allow better control over user privileges [privileges]

If this is related with the views and privileges, I'm on this
one!

Not sure what the problem is there. We already implement privileges on
views that are separate from the base tables.

I personally have not had any problems, but heard on the general list. Could
have been bad configuration, or wrong GRANTS. I didn't follow the thread so
closely.

Saludos... :-)

--
El mejor sistema operativo es aquel que te da de comer.
Cuida tu dieta.
-----------------------------------------------------------------
Martin Marques | mmarques@unl.edu.ar
Programador, Administrador | Centro de Telematica
Universidad Nacional
del Litoral
-----------------------------------------------------------------

At 01:20 PM 10-05-2001 -0400, Bruce Momjian wrote:

* Allow row re-use without vacuum (Vadim)

Will this do away with the need for a lazy vacuum?

Full text indexing.

This one is already done using GIST. The GIST improvements are in 7.1,
and I assume full text indexing will be more fully integrated into
PostgreSQL in 7.2.

I hope it will. What will the interface be like?

Wish I knew. :-)

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Bruce Momjian wrote:

Here is a small list of big TODO items. I was wondering which ones
people were thinking about for 7.2?

* Allow inherited tables to inherit index, UNIQUE constraint, and primary key
[inheritance]

i was wondering if there was any thought still being given to Oliver
Elphick's post from a while back that is still in TODO.detail
[inheritance]:
http://candle.pha.pa.us/mhonarc/todo.detail/inheritance/msg00010.html

i kind of feel as though the inheritance semantics for postgres at the
moment are not fully fleshed out, and including further features without
having a full plan for the semantics doesn't seem to advance the effort
of making postgres a true Object-Relational DBMS.

for my part, as a user, i am excited that inheritance is available even
in a limited fashion, but where i use it, i have basically had to invent
my own semantics for referential integrity based on a suite of triggers.
this issue is addressed in Oliver's post, but i was wondering if such
issues were still a part of the development dialogue since Oliver's post
was the last in TODO.detail [inheritance] and seemed to merit no
response (or any that i could find in the mailing list archives).

-tfo

From: <john@mwk.co.nz>
Date: Fri, 11 May 2001 10:41:57 +1200

Here is a small list of big TODO items. I was wondering which ones
people were thinking about for 7.2?

The need for stored procedures that return a record set.
This is required to migrate from MSSQL, Interbase and others.
This is a commonly requested item.

This would be very useful, as well as the "RETURNING" clause that is
supported elsewhere with inserts.

--
Virtually,
Ned Wolpert <ned.wolpert@knowledgenet.com>

D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45

Tom Lane writes:

Peter E. had implied that he wanted to tackle the elog issues for 7.2,
but I'm not sure if he's committed to it or not.

Well...

* Automatically add filename, line, function name: Easy to code, lots of
labour. Should be lumped in with some other large change.

* Error codes: I think there are only a handful of key messages that
users (programs) need to detect cleanly, mostly constraint violations.
The rest are "the query you sent is wrong -- fix your application" and
"something went really wrong -- manual repair needed"

So maybe this could be a smallish change.

* Translation: If we want to use gettext I can get started. I don't
think I'm interested in using any other interface.

--
Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter

Peter Eisentraut <peter_e@gmx.net> writes:

* Translation: If we want to use gettext I can get started. I don't
think I'm interested in using any other interface.

I have no objection to the gettext API, but I was and still am concerned
about depending on GNU gettext's code, because of license conflicts.
There is a BSD-license gettext clone project, but it doesn't look to be
very far along.

regards, tom lane