Re: PostgreSQL Project list for 2003 - Mailing list pgsql-advocacy

Include the IPC daemon for win32, assuming you still need it.

My biggest concerns for the future though are replication and longhorn.

Longhorn being the operating system that follows WinXP and it has a SQL
server-based file system. Regardless of whether it is the "Right thing to
do" or not (technically or politically), I think there will eventually be
demand for a Linux equivalent, particularly if  OSS is to dominate the
server room. There are only 2 open source databases currently up to the
task, Firebird and PostgreSQL. Maybe by the time it comes out MySQL will be
a real database by then. But whatever is available, the solution should be
able to replace SQL Server on the back end and provide equivalent services
for other OSs (Linux). I have no idea what it entails, it's actually
somewhat over my head in several respects. It'll probably have something to
go with .Net as well. It might just be some file system <-> blob functions,
I don't know.

Also that adds to the replication/backup bit because real-time fail over is
going to be needed if people are going to put vital files in the database,
and have them propagate corporate-wide. (I'm thinking about offices across
the globe)

One thing is certain. If PostgreSQL can provide it first, usage and
awareness will too.
-J

-----Original Message-----
From: pgsql-advocacy-owner@postgresql.org
[mailto:pgsql-advocacy-owner@postgresql.org]On Behalf Of Justin Clift
Sent: Thursday, November 28, 2002 12:27 PM
To: PostgreSQL Advocacy Mailing List
Subject: [pgsql-advocacy] PostgreSQL Project list for 2003


Hi everyone,

Was just thinking about key developments that would be interesting to
get up and running for PostgreSQL in the 2003 year.

First one that came to mind is this:

 - PostgreSQL Win32 installation package
  (PostgreSQL binary for Win32 + integrated GUI)

   * One-file downloadable full installation package
   * Installs PostgreSQL as a "service" on WinNT/2K/XP
   * Reasonable default memory configuration
   * Includes one of the good PostgreSQL cross-platform
     GUI's.  PgAccess?
   * No real end-user maintenance tasks for simple setups
     Auto-vacuums, auto-reindexes, auto-?
   * Includes inbuilt shortcuts to start/stop PostgreSQL,
     and to the included tools (PgAccess)
   * (maybe) By default, use XLOG files that are smaller
     than 16MB to reduce the installed footprint size
     for small setups.


Interesting potential results that spring to mind:

Bringing PG to the attention of, and into everyday usage by, a large
group of existing developers, some of whom will develop the GUI.

With a small-footprint (and fully functional) auto-maintaining PG
installation, integration with other products would be much more
practical.  Would be interesting to see if the OpenOffice developers
would find it suitable then, if nothing had already been included as
their default database.

Probably heaps of other benefits too (lowering migration risks and costs
from say MS SQL, etc)

Thankfully, none of this sounds like rocket science, just something that
would take a bit of time and effort to make reality.

Reckon this might be worth doing?

:-)

Regards and best wishes,

Justin Clift

--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
   - Indira Gandhi

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org