Shridhar Daithankar [EMAIL PROTECTED] writes:
Tom Lane wrote:
1. You can't easily generate a clean diff of your local version against
the original imported from postgresql.org. The changes you actually
made get buried in a mass of useless $Foo$ diff lines. Stripping those
out is possible
Christopher Kings-Lynne writes:
I'm just interested in what everyone's personal plans for 7.5
development are?
Here is a pretty good hit list:
http://developer.postgresql.org/docs/postgres/unsupported-features-sql99.html
There are still some low-hanging fruit and some
Alvaro Herrera writes:
(I will probably be doing lots of translation work too, or maybe enable
someone else to do it ...)
I think in 7.5 we'll be able to get everything fully translat{ed|able}.
We already have initdb, and we'll do ecpg, pg_ctl, and decide the fate of
initlocation and ipcclean.
On Thu, Nov 27, 2003 at 06:30:54PM +0100, Peter Eisentraut wrote:
Alvaro Herrera writes:
(I will probably be doing lots of translation work too, or maybe enable
someone else to do it ...)
I think in 7.5 we'll be able to get everything fully translat{ed|able}.
We already have initdb, and
Peter Eisentraut wrote:
Christopher Kings-Lynne writes:
I'm just interested in what everyone's personal plans for 7.5
development are?
There are still some low-hanging fruit and some
below-the-cloudy-sky-hanging fruit in there, for instance
[...snip...]
Basic array support
^^^
Hi everyone,
I'm just interested in what everyone's personal plans for 7.5
development are?
Shridar, Gavin and myself are trying to get the tablespaces stuff off
the ground. Hopefully we'll have a CVS set up for us to work in at some
point (we didn't think getting a branch and commit privs
On Thu, Nov 27, 2003 at 10:27:22AM +0800, Christopher Kings-Lynne wrote:
What's everyone else wanting to work on?
I want to get the nested transaction patch thingie sorted out.
I feel it's not that far away. After that, maybe
- try using a pg_shareddepend shared catalog to check user
On Thu, 27 Nov 2003, Christopher Kings-Lynne wrote:
Changing all our $Id$ tags to $Postgres$ would make a separate CVS a lot
easier, hint hint :)
Why? From the info pages:
`$Header$'
A standard header containing the full pathname of the RCS file,
the revision number, the date
So, what does changing it to $PostgreSQL$ do? Or am I reading the wrong
part of the manual?
After applying the patch in -patches to CVSROOT and running the update
script...
It will allow Chris and other to import the PostgreSQL source into their
own CVS tree without having do to a ton of diff
On Wed, 26 Nov 2003, Rod Taylor wrote:
So, what does changing it to $PostgreSQL$ do? Or am I reading the wrong
part of the manual?
After applying the patch in -patches to CVSROOT and running the update
script...
It will allow Chris and other to import the PostgreSQL source into their
Rod Taylor [EMAIL PROTECTED] writes:
So, what does changing it to $PostgreSQL$ do? Or am I reading the wrong
part of the manual?
The BSDs wen't through similar measures to ensure they could maintain
multiple CVS sources without diff / patch going nuts.
Yeah, I have gotten similar requests
Marc G. Fournier [EMAIL PROTECTED] writes:
'k, but why can't that be accomplished with $Id$?
$Id$ isn't much better than $Header$ --- the point is to avoid keywords
that downstream people's CVS repositories will want to replace.
Are there any caveats to the change? Ie. if Tom has a checkout
On Wed, 2003-11-26 at 23:32, Marc G. Fournier wrote:
On Wed, 26 Nov 2003, Rod Taylor wrote:
So, what does changing it to $PostgreSQL$ do? Or am I reading the wrong
part of the manual?
After applying the patch in -patches to CVSROOT and running the update
script...
It will allow
Christopher Kings-Lynne wrote:
Hi everyone,
I'm just interested in what everyone's personal plans for 7.5
development are?
Shridar, Gavin and myself are trying to get the tablespaces stuff off
the ground. Hopefully we'll have a CVS set up for us to work in at some
point (we didn't think
Rod Taylor [EMAIL PROTECTED] writes:
On Wed, 2003-11-26 at 23:32, Marc G. Fournier wrote:
'k, but why can't that be accomplished with $Id$?
When you import the files into the other CVS system the version and file
information $Id$ represents will be replaced by the other system. So,
when you
Tom Lane wrote:
1. You can't easily generate a clean diff of your local version against
the original imported from postgresql.org. The changes you actually
made get buried in a mass of useless $Foo$ diff lines. Stripping those
out is possible in theory but painful.
Is that the reason linux does
16 matches
Mail list logo
