Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> There is also a lot of other functionality that throws "not implemented"
> errors if you try to use 2PC with them. For example, DDL and
> notifications.
Why would DDL be different from any other query?
regards, tom lane
---
On Thu, 27 May 2004, Christopher Browne wrote:
> [EMAIL PROTECTED] (Bruce Momjian) wrote:
> > Win32 has 98% of its code in CVS, so it will make it
> > Tablespaces - Christopher says it is ready, and has run tests
> > PITR - some functionality might be in 7.5, but we aren't sure
> >
Christopher Browne <[EMAIL PROTECTED]> writes:
> PITR may turn out to be a "don't care" item if Slony1 winds up
> providing its own approach to PITR. (e.g. - if you write out to
> disk the sets of SQL statements that are to be applied to a replica,
> then the spooled sets of these statements rep
The world rejoiced as [EMAIL PROTECTED] (Greg Stark) wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
>
>> Greg Stark <[EMAIL PROTECTED]> writes:
>> > This is the only place where I see hardly any movement on major
>> > items the whole development cycle, then a rush of radical changes
>> > just before
[EMAIL PROTECTED] (Bruce Momjian) wrote:
> Win32 has 98% of its code in CVS, so it will make it
> Tablespaces - Christopher says it is ready, and has run tests
> PITR - some functionality might be in 7.5, but we aren't sure
> Nested transactions - Alvaro thinks it is close,
Tom Lane <[EMAIL PROTECTED]> writes:
> Greg Stark <[EMAIL PROTECTED]> writes:
> > This is the only place where I see hardly any movement on major items the
> > whole development cycle, then a rush of radical changes just before the
> > freeze.
>
> [blink] There's been plenty of stuff done all t
Greg Stark <[EMAIL PROTECTED]> writes:
> This is the only place where I see hardly any movement on major items the
> whole development cycle, then a rush of radical changes just before the
> freeze.
[blink] There's been plenty of stuff done all through this development
cycle (and previous ones to
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Reality check --- why should they keep going if the stuff if appication
> is going to be months away, and these big features are going to change
> CVS significantly anyway?
>
> Let's be honest --- if they aren't going to make it, they will stop
> work
On Fri, 28 May 2004, Bruce Momjian wrote:
Marc G. Fournier wrote:
On Fri, 28 May 2004, Bruce Momjian wrote:
Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
Off the top of my head ... the Installer and Service Manager come to mind
... and Tom's fsync changes ...
Right now, I'd say fe
Marc G. Fournier wrote:
> On Fri, 28 May 2004, Bruce Momjian wrote:
>
> > Tom Lane wrote:
> >> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> >>> Off the top of my head ... the Installer and Service Manager come to mind
> >>> ... and Tom's fsync changes ...
> >>
> >>> Right now, I'd say feature
On Fri, 28 May 2004, Bruce Momjian wrote:
Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
Off the top of my head ... the Installer and Service Manager come to mind
... and Tom's fsync changes ...
Right now, I'd say feature freeze is looking more like next Friday (June
4th), and we'r
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Off the top of my head ... the Installer and Service Manager come to mind
> ... and Tom's fsync changes ...
> Right now, I'd say feature freeze is looking more like next Friday (June
> 4th), and we're evaluate it then ... that should hopefully giv
On Fri, 28 May 2004, Magnus Hagander wrote:
Today is May 28. So if nobody will not commit above within 3
days, non
of them will be in 7.5(8.0). Am I correct?
Not necessarily ... there are several Win32 related features
that still
haven't been committed (that I've seen) that will push back
the relea
>> Today is May 28. So if nobody will not commit above within 3
>days, non
>> of them will be in 7.5(8.0). Am I correct?
>
>Not necessarily ... there are several Win32 related features
>that still
>haven't been committed (that I've seen) that will push back
>the release,
>and hopefully give so
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Off the top of my head ... the Installer and Service Manager come to mind
> > ... and Tom's fsync changes ...
>
> > Right now, I'd say feature freeze is looking more like next Friday (June
> > 4th), and we're evaluate it then .
> I certainly get the feeling that things are being rushed just a bit too
> much, and think having a extra few days of breathing space makes sense.
>
> cheers
>
> andrew
I have that feeling too, and I'm working still working on pg_autovacuum
integration which I was hoping to get in, so I would we
On Fri, 28 May 2004, Andrew Dunstan wrote:
The Installer is a pgFoundry project, and unaffected by feature freeze.
See http://pginstaller.projects.postgresql.org (Note: Magnus hasn't put
anything there yet, though.)
'k, wasn't sure about that one ... but the SVC and fsync stuff is still
outstand
Marc G. Fournier wrote:
On Fri, 28 May 2004, Tatsuo Ishii wrote:
Hi Bruce,
Is that core's decision that:
o below all four major features will be incorporated into 7.5
We don't know. If they can be added to CVS without major changes,
they
will be in 7.5. As far as I can tell:
Win32 has 98%
Marc G. Fournier wrote:
Right now, I'd say feature freeze is looking more like next Friday (June
4th), and we're evaluate it then ... that should hopefully give the
above time to flesh out and get into CVS ...
Speaking of CVS, a CERT advisory was issued yesterday documenting a
vulnerability:
ht
On Fri, 28 May 2004, Tatsuo Ishii wrote:
Hi Bruce,
Is that core's decision that:
o below all four major features will be incorporated into 7.5
We don't know. If they can be added to CVS without major changes, they
will be in 7.5. As far as I can tell:
Win32 has 98% of its code in CVS, so
> > > Hi Bruce,
> > >
> > > Is that core's decision that:
> > >
> > > o below all four major features will be incorporated into 7.5
> >
> > We don't know. If they can be added to CVS without major changes, they
> > will be in 7.5. As far as I can tell:
> >
> > Win32 has 98% of its code in
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tatsuo Ishii wrote:
>> Ok, BTW have we decided that next verison is marked as 7.5 or 8.0?
> No. Some argue that an 8.0 should only be done if we break backward
> compatibility, while others feel major features should cause an 8.0.
In any case, it's prem
Tatsuo Ishii wrote:
> Ok, BTW have we decided that next verison is marked as 7.5 or 8.0?
No. Some argue that an 8.0 should only be done if we break backward
compatibility, while others feel major features should cause an 8.0.
--
Bruce Momjian| http://candle.pha.pa.us
Ok, BTW have we decided that next verison is marked as 7.5 or 8.0?
--
Tatsuo Ishii
> Tatsuo Ishii wrote:
> > Hi Bruce,
> >
> > Is that core's decision that:
> >
> > o below all four major features will be incorporated into 7.5
>
> We don't know. If they can be added to CVS without major change
Tatsuo Ishii wrote:
> Hi Bruce,
>
> Is that core's decision that:
>
> o below all four major features will be incorporated into 7.5
We don't know. If they can be added to CVS without major changes, they
will be in 7.5. As far as I can tell:
Win32 has 98% of its code in CVS, so it will
Nearing our June 1 feature freeze, we now have patches for all our major
outstanding features. Their status is:
Win32 - almost done, fsync needed, bug fixes, etc
PITR - Simon is away until Sunday and we are working on it
Nested transactions - patch needs review, trigger iss
Hi Bruce,
Is that core's decision that:
o below all four major features will be incorporated into 7.5
o beta freeze will be June 1
In the upcoming big event "Linux World" (in Tokyo, from June 2 to 4) I
need to present about current status of PostgreSQL development. Even
if cores have not decided
27 matches
Mail list logo
