Skip site navigation (1) Skip section navigation (2)

Re: Developer TODO List as a PostgreSQL DB

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Chad Wagner <chad(dot)wagner(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, deductive(at)kutoma(dot)com
Subject: Re: Developer TODO List as a PostgreSQL DB
Date: 2007-02-27 16:31:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> And, for the record, I do not see the slightest point in putting the
> TODO list on its own into a database. None, zilch, nada. As database
> professionals we should be adept at recognising when the use of a
> database is appropriate and when it isn't. If we put it into a tracking
> system (presumably database backed) that would be another matter, but
> that has gone nowhere as usual.

As someone who has been involved in these discussions over and over, I
would suggest that everyone just drop the whole thing. It won't go
anywhere, and it just isn't worth the 3 cents of bandwidth it would cost
to send the emails.

Joshua D. Drake


      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997

Donate to the PostgreSQL Project:
PostgreSQL Replication:

In response to

pgsql-hackers by date

Next:From: Jim C. NasbyDate: 2007-02-27 16:37:45
Subject: Re: Resumable vacuum proposal and design overview
Previous:From: Jim C. NasbyDate: 2007-02-27 16:30:20
Subject: Re: autovacuum next steps, take 2

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group