On Tue, Aug 7, 2012 at 8:51 AM, Magnus Hagander wrote:
> Agreed. Anybody up for writing the text though? There was some text
> earlier (see
> http://git.postgresql.org/gitweb/?p=pgweb.git;a=commitdiff;h=bd02e36141bb99e9ee4e0b80fd69464e0e6d91b7#patch18
> or the corresponding one in the old pgweb r
On Tue, Aug 7, 2012 at 2:44 PM, Robert Haas wrote:
> On Mon, Aug 6, 2012 at 11:22 PM, Craig Ringer wrote:
>> Heya all
>>
>> It seems like it's a bit trickier to find beta downloads than might be
>> ideal.
>>
>> The beta info page simply reads:
>>
>> " PostgreSQL 9.2 beta 3 was released on Aug
On Mon, Aug 6, 2012 at 11:22 PM, Craig Ringer wrote:
> Heya all
>
> It seems like it's a bit trickier to find beta downloads than might be
> ideal.
>
> The beta info page simply reads:
>
> " PostgreSQL 9.2 beta 3 was released on August 6, 2012."
>
> with no information about how to obtain a bu
Heya all
It seems like it's a bit trickier to find beta downloads than might be
ideal.
The beta info page simply reads:
" PostgreSQL 9.2 beta 3 was released on August 6, 2012."
with no information about how to obtain a build or the sources, not even
a link to the downloads page, despite
Josh Berkus writes:
>> How are we handling the Monday release with everyone at PGCon? Was that
>> resolved?
> I have yet to see a confirmed date, guys. If we expect any support from
> the packagers and/or the advocacy volunteers, then people need at least
> a week's notice, probably more.
I ha
>> Next week, I thought.
>
> How are we handling the Monday release with everyone at PGCon? Was that
> resolved?
I have yet to see a confirmed date, guys. If we expect any support from
the packagers and/or the advocacy volunteers, then people need at least
a week's notice, probably more.
--
On Wed, May 02, 2012 at 01:15:48PM -0400, Tom Lane wrote:
> Peter Eisentraut writes:
> > On ons, 2012-05-02 at 00:31 -0400, Tom Lane wrote:
> >> Checking this patch, I noticed that config.guess and config.sub harbor
> >> most of the remaining references to those platforms, which reminded me:
> >>
Pavel Stehule wrote:
> Hello
>
> it fixes bug
>
> pg_upgrade(13359) malloc: *** error for object 0x801600:
> non-page-aligned, non-allocated pointer being freed
> *** set a breakpoint in malloc_error_break to debug
>
>
> arget 03:31 /usr/local/src/postgresql/contrib/pg_upgrade git diff .
> diff
Pavel Stehule writes:
> --- a/contrib/pg_upgrade/check.c
> +++ b/contrib/pg_upgrade/check.c
> @@ -154,7 +154,6 @@ issue_warnings(migratorContext *ctx, char
> *sequence_script_file_name)
> ctx->new.bindir,
> ctx->new.port, sequence_script_file_name,
>
Pavel Stehule writes:
> postgres=# explain SELECT name
> FROM person
> WHERE name IN (
>SELECT name FROM person p
>LEFT JOIN person_data ON p.id = person_data.id);
> ERROR: failed to build any 2-way joins
Fixed, thanks.
regards, tom lane
--
Sent via pgs
On Fri, May 21, 2010 at 10:11 PM, Pavel Stehule wrote:
> it fixes bug
>
> pg_upgrade(13359) malloc: *** error for object 0x801600:
> non-page-aligned, non-allocated pointer being freed
> *** set a breakpoint in malloc_error_break to debug
>
>
> arget 03:31 /usr/local/src/postgresql/contrib/pg_upgr
Hello
it fixes bug
pg_upgrade(13359) malloc: *** error for object 0x801600:
non-page-aligned, non-allocated pointer being freed
*** set a breakpoint in malloc_error_break to debug
arget 03:31 /usr/local/src/postgresql/contrib/pg_upgrade git diff .
diff --git a/contrib/pg_upgrade/check.c b/contr
Hello
there are maybe planner bug.
test case:
CREATE TABLE person (
id SERIAL PRIMARY KEY,
name VARCHAR(64)
) WITHOUT OIDS;
CREATE TABLE person_data (
id SERIAL PRIMARY KEY
) WITHOUT OIDS;
SELECT name
FROM person
WHERE name IN (
On Sat, 2010-05-08 at 08:12 -0400, Robert Haas wrote:
> (3) mentoring the GSoC
> projects on matviews, json, and merge. Everything else is pretty
> amorphous at this point,
That's good you volunteered. I'm sorry to say that I'm really surprised
to hear anyone thinks MERGE or matviews are suitabl
On Sat, May 8, 2010 at 6:34 AM, Simon Riggs wrote:
> I've often faced the issue you describe. I think its difficult for
> everybody to help at this stage. In many ways it is a serialization and
> it's good that Tom holds the gate tighter than normal at this point.
>
> The main thing I've tried to
On Sat, May 8, 2010 at 12:04 AM, Marc G. Fournier wrote:
> IMHO, there is nothing wrong with you (or any other developer) spending time
> working on v9.1 features if said person feels that they have satisfied
> themselves that v9.0 is ready for release (ie. I think the best test anyone
> can run,
On Fri, 2010-05-07 at 18:26 -0400, Robert Haas wrote:
> On Fri, May 7, 2010 at 5:35 PM, Tom Lane wrote:
> > Robert Haas writes:
> >> [ argues, in effect, for starting 9.1 development right now ]
> >
> > I can't stop you from spending your time as you please. My development
> > time for at least
On Fri, 7 May 2010, Robert Haas wrote:
On Fri, May 7, 2010 at 5:35 PM, Tom Lane wrote:
Robert Haas writes:
[ argues, in effect, for starting 9.1 development right now ]
I can't stop you from spending your time as you please. My development
time for at least the next month or two is going
On Fri, May 7, 2010 at 5:35 PM, Tom Lane wrote:
> Robert Haas writes:
>> [ argues, in effect, for starting 9.1 development right now ]
>
> I can't stop you from spending your time as you please. My development
> time for at least the next month or two is going to be spent on
> code-reading the H
Robert Haas writes:
> [ argues, in effect, for starting 9.1 development right now ]
I can't stop you from spending your time as you please. My development
time for at least the next month or two is going to be spent on
code-reading the HS/SR code and fixing bugs as they come in. I don't
foresee
On Fri, May 7, 2010 at 11:31 AM, Tom Lane wrote:
> I would say the expectation for individual developers is "test, and
> read code". It's certainly not time to be starting new feature
> development yet.
I am humbly of the opinion that the expectation you have enclosed in
quotation marks is far t
Robert Haas writes:
> I am fuzzier on what happens now. I understand that it depends on
> what bug reports we get as a result of beta testing, but what I don't
> quite know is what the expectations are for individual developers, how
> we're tracking what issues still need to be resolved, or what
On Mon, Jan 11, 2010 at 10:45 PM, Bruce Momjian wrote:
>> > What amazes me is how many people who closely follow our development are
>> > mystified by what we do during that pre-beta period.
>>
>> Hey, I'm still mystified. Maybe you and Tom could do twice-a-week
>> status updates on what you're w
Robert Haas writes:
> I think it might be time to think about shipping a beta release. I
> guess this is a -core decision, but I can't argue for it there, so
> I'll argue for it here. It seems like we're about ready, so maybe we
> could plan for a beta, say, a week from now?
A bit of discussion
On Thu, Apr 22, 2010 at 12:18 PM, Marc G. Fournier wrote:
> We're discussing scheduling on -core right now, triggered by your email, and
> will put out a notice shortly ... although we did just do a back branch
> release, we have a second one that has to be done, so we're trying to
> balance sched
On Thu, 22 Apr 2010, Robert Haas wrote:
On Wed, Apr 21, 2010 at 9:41 AM, Marc G. Fournier wrote:
On Wed, 21 Apr 2010, Robert Haas wrote:
Well, never mind that then. How about a beta next week?
I'm good for that ...
Anyone else want to weigh in for or against this?
We're discussing sche
On Wed, Apr 21, 2010 at 9:41 AM, Marc G. Fournier wrote:
> On Wed, 21 Apr 2010, Robert Haas wrote:
>> Well, never mind that then. How about a beta next week?
>
> I'm good for that ...
Anyone else want to weigh in for or against this?
...Robert
--
Sent via pgsql-hackers mailing list (pgsql-hac
On Wed, 21 Apr 2010, Robert Haas wrote:
Well, never mind that then. How about a beta next week?
I'm good for that ...
Marc G. FournierHub.Org Hosting Solutions S.A.
scra...@hub.org http://www.hub.org
Yahoo:yscrappySkype: h
On Tue, Apr 20, 2010 at 1:53 PM, Marc G. Fournier wrote:
> On Tue, 20 Apr 2010, Robert Haas wrote:
>
>> /me pushes luck
>>
>> And how about a set of back-branch releases while we're at it?
>
> We tend to try and avoid overlapping a "release" with a "beta" to avoid
> confusion ... but didn't we jus
On Tue, Apr 20, 2010 at 4:08 PM, Josh Berkus wrote:
>> Improve behavior of SUSET GUC variables added by loadable modules?
>> - Tom's looking at this, too.
>
> Is this an issue specific to 9.0?
http://archives.postgresql.org/pgsql-hackers/2010-04/msg00865.php
...Robert
--
Sent via pgsql-hackers
> - Fix to_char('L') (localization) on Win32 when the operating system
> character encoding does not match the database encoding
> Seems like we're close to a fix on this, but even if not, I don't see
> why this should be considered a blocker for beta.
If this isn't an issue specific to 9.0, I ag
On Tue, Apr 20, 2010 at 6:37 PM, Joshua D. Drake wrote:
> On Tue, 2010-04-20 at 18:23 +0100, Dave Page wrote:
>> On Tue, Apr 20, 2010 at 6:09 PM, Robert Haas wrote:
>>
>> > /me pushes luck
>> >
>> > And how about a set of back-branch releases while we're at it?
>>
>> Yes, please don't push your l
On Tue, 20 Apr 2010, Robert Haas wrote:
/me pushes luck
And how about a set of back-branch releases while we're at it?
We tend to try and avoid overlapping a "release" with a "beta" to avoid
confusion ... but didn't we just do a fresh back branch release anyway?
Marc G. Fournier
On Tue, 2010-04-20 at 18:23 +0100, Dave Page wrote:
> On Tue, Apr 20, 2010 at 6:09 PM, Robert Haas wrote:
>
> > /me pushes luck
> >
> > And how about a set of back-branch releases while we're at it?
>
> Yes, please don't push your luck :-p
/me gives Dave an "Easy" button.
>
>
>
> --
> Dave
On Tue, Apr 20, 2010 at 6:09 PM, Robert Haas wrote:
> /me pushes luck
>
> And how about a set of back-branch releases while we're at it?
Yes, please don't push your luck :-p
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-hackers
I think it might be time to think about shipping a beta release. I
guess this is a -core decision, but I can't argue for it there, so
I'll argue for it here. It seems like we're about ready, so maybe we
could plan for a beta, say, a week from now?
Here's a quick run-down of the remaining open it
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I think we need a beta2 now, and perhaps RC1 in a week. We've done
>> enough portability hacking recently that some more beta seems indicated.
> OK, what steps do we need to do to get beta2 out?
I think all we really gotta do is upda
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Where are we on releasing beta2 or perhaps going right to an RC1
> > release? Seems it is time for one of them.
>
> I think we need a beta2 now, and perhaps RC1 in a week. We've done
> enough portability hacking recently that some m
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Where are we on releasing beta2 or perhaps going right to an RC1
> release? Seems it is time for one of them.
I think we need a beta2 now, and perhaps RC1 in a week. We've done
enough portability hacking recently that some more beta seems indicated.
Where are we on releasing beta2 or perhaps going right to an RC1
release? Seems it is time for one of them.
--
Bruce Momjian [EMAIL PROTECTED]
EnterpriseDBhttp://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---(end of bro
I know we were planning for beta today or Monday, but few new items have
crept up and it will take a few more days to enter beta, so look for
beta sometime next week.
FYI, I will be off-line for the next 24 hours.
--
Bruce Momjian| http://candle.pha.pa.us
pgman@candl
FYI, with the patch queue shrinking, it is time to consider a date for
beta. The current plan is to start beta in 7-10 days, so possible dates
are August 19 or 22.
We will need to have all major patches addressed, the release notes
done, and the major documentation usable.
--
Bruce Momjian
FYI, I am going to need a few more days to apply patches submitted in
the past few days and Magnus needs a few more days to fix the windows
signal problems. So, rather than planning a beta for later this week, I
think we should focus on early next week.
--
Bruce Momjian
Buskermolen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: "pgsql-hackers" <[EMAIL PROTECTED]>
Sent: Thu, 28 Oct 2004 10:35:04 -0700
Subject: Re: [HACKERS] Beta 4 on Debian Sarge (MIPS/MIPSEL)
> On October 27, 2004 05:57 pm, Jim Buttafuoco wrote:
> > Hackers,
> >
> &
On October 27, 2004 05:57 pm, Jim Buttafuoco wrote:
> Hackers,
>
> just an fyi, Beta 4 passed ALL tests on Debian Sarge for both MIPS (Indy)
> and MIPSEL (Cobalt RAQ)
>
> I can test Debian Sarge Sparc, Alpha, PowerPC, PA-RISC and M68K if no one
> else has reported on these systems yet.
>
> Also, wi
"Jim Buttafuoco" <[EMAIL PROTECTED]> writes:
> I can test Debian Sarge Sparc, Alpha, PowerPC, PA-RISC and M68K if no one else has
> reported on these systems yet.
> Also, with a little work I could test Solaris, Tru64 (or what ever its called these
> days) and IRIX
You should probably wait till
Hackers,
just an fyi, Beta 4 passed ALL tests on Debian Sarge for both MIPS (Indy) and MIPSEL
(Cobalt RAQ)
I can test Debian Sarge Sparc, Alpha, PowerPC, PA-RISC and M68K if no one else has
reported on these systems yet.
Also, with a little work I could test Solaris, Tru64 (or what ever its ca
Daniel Schuchardt <[EMAIL PROTECTED]> writes:
> duplicate key violates unique constraint "ferber_rust_params_pkey"
> FATAL: block 0 of 1663/19335/476756 is still referenced (local 2)
> server closed the connection unexpectedly
This is already fixed, but thanks for the report!
Hi List, I have another error now here:
notice that only one backend is dying, all others are up and working.
Error - Message :
duplicate key violates unique constraint "ferber_rust_params_pkey"
FATAL: block 0 of 1663/19335/476756 is still referenced (local 2)
server closed the connection unexpect
MAIL PROTECTED]>
Sent: Mon, 30 Aug 2004 13:23:03 -0400
Subject: Re: [HACKERS] beta 1 failed on linux mipsel
> "Jim Buttafuoco" <[EMAIL PROTECTED]> writes:
> > I have confirmed that 7.4.3 works on the cobalt raq mipsel system. I
> > have not looked at the s_lock.[c
ok, will look at it in the morning.
-- Original Message ---
From: Tom Lane <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: "pgsql-hackers" <[EMAIL PROTECTED]>
Sent: Sun, 29 Aug 2004 21:42:57 -0400
Subject: Re: [HACKERS] beta 1 failed on linux mipsel
>
"Jim Buttafuoco" <[EMAIL PROTECTED]> writes:
> Shouldn't this also work on mipsel CPU's?
It should work on a real MIPS CPU. The PlayStation 2 has a dumbed-down
MIPS chip without the TAS instruction :-(, but now that we've eliminated
that point I think you've found a problem. We made several
reor
-- Original Message ---
From: Tom Lane <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: "pgsql-hackers" <[EMAIL PROTECTED]>
Sent: Sun, 29 Aug 2004 15:27:32 -0400
Subject: Re: [HACKERS] beta 1 failed on linux mipsel
> "Jim Buttafuoco" <[EMAIL PROTECTE
"Jim Buttafuoco" <[EMAIL PROTECTED]> writes:
> trying to test beta 1 on Debian linux mipsel (sarge).
What is that, a playstation 2? Last we heard, that chip had no spinlock
support. Did you use configure --disable-spinlocks?
regards, tom lane
---
trying to test beta 1 on Debian linux mipsel (sarge). I am getting the following
error "PANIC: stuck spinlock
(0x2b052030) detected at lwlock.c:246" during initdb. here is the complete initdb run.
[EMAIL PROTECTED]:~$ initdb
The files belonging to this database system will be owned by user "p
On Monday 09 August 2004 13:15, Josh Berkus wrote:
> 1) track platform tests, namely which platforms have been tested, what they
> reported, and which have not, including soliciting on the lists for more
> platform testers;
I wonder, would folks be interested in keeping a "supported programs" list
Updated ...
On Mon, 9 Aug 2004, Marc G. Fournier wrote:
I'll be modifying that tonight ...
On Mon, 9 Aug 2004, Serguei A. Mokhov wrote:
Maybe this should be brought up-to-date slightly?
http://developer.postgresql.org/beta.php
Or maybe point elsewhere at least where the more up-to-date info actuall
I'll be modifying that tonight ...
On Mon, 9 Aug 2004, Serguei A. Mokhov wrote:
Maybe this should be brought up-to-date slightly?
http://developer.postgresql.org/beta.php
Or maybe point elsewhere at least where the more up-to-date info actually
is.
--
Serguei A. Mokhov| /~\The ASCI
This is the kind of thing I can usually help with.
However, right now I'm a little swamped with customer work.
I can back someone up, though.
--elein
On Mon, Aug 09, 2004 at 06:28:33PM -0400, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On Mon, 9 Aug 2004, Josh Berkus wrote:
> >
> > > Folk
Maybe this should be brought up-to-date slightly?
http://developer.postgresql.org/beta.php
Or maybe point elsewhere at least where the more up-to-date info actually
is.
--
Serguei A. Mokhov| /~\The ASCII
Computer Science Department | \ / Ribbon Campaign
Concordia University
Marc G. Fournier wrote:
> On Mon, 9 Aug 2004, Josh Berkus wrote:
>
> > Folks,
> >
> > Per our discussion earlier this year, I really think that we could shorten the
> > beta process and make it more effective if someone can step forward to be the
> > "8.0 Beta Leader." This person would have to:
Marc,
> Is there a reason why Bruce isn't doing it like he has for all previous
> releases? As he previously held such a role, shouldn't it be he calling
> for someone to take over that role from him?
Clearly I was confused about the import of a discussion we had on Core, some 3
months ago or
On Mon, 9 Aug 2004, Josh Berkus wrote:
Folks,
Per our discussion earlier this year, I really think that we could shorten the
beta process and make it more effective if someone can step forward to be the
"8.0 Beta Leader." This person would have to:
1) track platform tests, namely which platforms
On Mon, 2004-08-09 at 13:57, Peter Eisentraut wrote:
> Josh Berkus wrote:
> > Per our discussion earlier this year, I really think that we could
> > shorten the beta process and make it more effective if someone can
> > step forward to be the "8.0 Beta Leader." This person would have
> > to:
> >
Josh Berkus wrote:
> Per our discussion earlier this year, I really think that we could
> shorten the beta process and make it more effective if someone can
> step forward to be the "8.0 Beta Leader." This person would have
> to:
> 1) track platform tests, namely which platforms have been tested,
Folks,
Per our discussion earlier this year, I really think that we could shorten the
beta process and make it more effective if someone can step forward to be the
"8.0 Beta Leader." This person would have to:
1) track platform tests, namely which platforms have been tested, what they
reporte
OK, I fixed the Win32 pgport build problem with Claudio's help.
I also fixed pg_dumpall on Win32 at the same time.
I might be out most of the day tomorrow.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life
Alvaro Herrera wrote:
Whitespace where?
OK, clarified:
Syntax checking of array input processing has been tighened up
considerably. Junk that was previously allowed in odd places with
odd results now causes an ERROR. Also changed behavior with respect
to whitespace surrounding array eleme
On Sat, Aug 07, 2004 at 10:09:22PM -0700, Joe Conway wrote:
>
>
>Syntax checking of array input processing has been tighened up
>considerably. Junk that was previously allowed in odd places with
>odd results now causes an ERROR. Also changed behavior with respect
>to whitespac
Tom Lane wrote:
Minor gripe: this bit of documentation seems out of date now.
!For example, elements containing curly braces, commas (or whatever the
!delimiter character is), double quotes, backslashes, or leading white
!space must be double-quoted. To put a double quote or backslash
Joe Conway <[EMAIL PROTECTED]> writes:
> I committed the attached.
Minor gripe: this bit of documentation seems out of date now.
!For example, elements containing curly braces, commas (or whatever the
!delimiter character is), double quotes, backslashes, or leading white
!space must b
Joe Conway wrote:
> Tom Lane wrote:
> > Joe Conway <[EMAIL PROTECTED]> writes:
> >>1. '{{"1 2" x},{3}}'
> >>2. '{{},{}}'
> >
> >>My patch would generate an ERROR for either. Tom, you questioned my
> >>disallowing of both of these, but didn't seem to have a very strong
> >>opinion.
> >
> > I don
Tom Lane wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
1. '{{"1 2" x},{3}}'
2. '{{},{}}'
My patch would generate an ERROR for either. Tom, you questioned my
disallowing of both of these, but didn't seem to have a very strong
opinion.
I don't have any great love for the first item --- I think it
On Sat, 7 Aug 2004, Tom Lane wrote:
The plan was to wrap beta1 sometime tomorrow ... I'd guess that
"sometime" will end up being in the afternoon east coast time, but this
largely depends on the libpgport breakage ...
That's what I was figuring (re: libpgport) ... hopefully I'm following the
rig
Joe Conway <[EMAIL PROTECTED]> writes:
> I was waiting on feedback on two issues before committing:
> 1. '{{"1 2" x},{3}}'
> 2. '{{},{}}'
> My patch would generate an ERROR for either. Tom, you questioned my
> disallowing of both of these, but didn't seem to have a very strong
> opinion.
I don
Joe Conway wrote:
> Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> >>Tom, when you updated the release notes, did you do a CVS log and
> >>already get all the new stuff as of Aug 6?
> >
> > Yes I did. I think the release notes are good to go for beta,
> > with the possible except
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Tom, when you updated the release notes, did you do a CVS log and
already get all the new stuff as of Aug 6?
Yes I did. I think the release notes are good to go for beta,
with the possible exception of mentioning any array-input-parsing
hac
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> I have two things left before beta. I want to make sure the release
> >> notes are current against CVS and I want to make sure the win32
> >> tablespace symlink changes I just made work.
>
> > Tom, when you updated the release notes,
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> I have two things left before beta. I want to make sure the release
>> notes are current against CVS and I want to make sure the win32
>> tablespace symlink changes I just made work.
> Tom, when you updated the release notes, did you do a CVS log and
>
Bruce Momjian wrote:
> I have two things left before beta. I want to make sure the release
> notes are current against CVS and I want to make sure the win32
> tablespace symlink changes I just made work.
>
Tom, when you updated the release notes, did you do a CVS log and
already get all the new s
I have two things left before beta. I want to make sure the release
notes are current against CVS and I want to make sure the win32
tablespace symlink changes I just made work.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
> OK, we scheduled beta for August 1, and we are close, but we should get
> a few more patches in before bundling beta. I have applied all I could
> from the patch queue. Tom needs to review the rest.
Of my three patches, they are all "bug fixes", however the USING INDEX
TABLESPACE one should pr
> OK, we scheduled beta for August 1, and we are close, but we should get
> a few more patches in before bundling beta. I have applied all I could
> from the patch queue. Tom needs to review the rest.
Oh, and perhaps once the owner/acl fix patch is in, then whoever commits
Fabien's patch to fix
OK, we scheduled beta for August 1, and we are close, but we should get
a few more patches in before bundling beta. I have applied all I could
from the patch queue. Tom needs to review the rest.
Plus we have a nested transaction patch to apply and a little PITR work
left to do. We should be abl
On Mon, 2004-07-12 at 18:49, Bruce Momjian wrote:
> Our current release schedule is:
>
> o apply most oustanding patches this week
> o take two weeks to finalize open issues
> o beta August 1
I will work to support this timeline.
I'm still hacking at the stop-at-point-in-tim
Our current release schedule is:
o apply most oustanding patches this week
o take two weeks to finalize open issues
o beta August 1
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your lif
FYI, we are currently scheduled for beta on Monday. Tom and I are both
still cleaning up things.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be y
> "Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> > Let's start beta July 18 or that weekend. I can catch up with email by
> > then, and Tom will have the elog() changes done by then too.
>
> What about the PITR ( point in time recovery )?
> I mean: the 7.4 will have PITR or not ?
Nope.
Chris
-
"Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> Let's start beta July 18 or that weekend. I can catch up with email by
> then, and Tom will have the elog() changes done by then too.
What about the PITR ( point in time recovery )?
I mean: the 7.4 will have PITR or not ?
Thank you in advance
Gaetan
OK. Roger.
---
The Hermit Hacker wrote:
> On Wed, 9 Jul 2003, Bruce Momjian wrote:
>
> >
> > Let's start beta July 18 or that weekend. I can catch up with email by
> > then, and Tom will have the elog() changes done by th
On Wed, 9 Jul 2003, Bruce Momjian wrote:
>
> Let's start beta July 18 or that weekend. I can catch up with email by
> then, and Tom will have the elog() changes done by then too.
Let's make it July 21st then ... I'm with family next week in the middle
of nowhere in a tent ... not even sure if I'
Let's start beta July 18 or that weekend. I can catch up with email by
then, and Tom will have the elog() changes done by then too.
---
Bruce Momjian wrote:
> You might have noticed I am behind on email.
>
> I had a big fa
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> On FreeBSD/Alpha, all 89 tests pass.
> I get this build warning though:
> gcc -pipe -O -Wall -Wmissing-prototypes -Wmissing-declarations -I. -I../../.
> ./src/include -c -o gram.o gram.c
> In file included from gram.y:7725:
> scan.l: In fun
On FreeBSD/Alpha, all 89 tests pass.
I get this build warning though:
gcc -pipe -O -Wall -Wmissing-prototypes -Wmissing-declarations -I. -I../../.
./src/include -c -o gram.o gram.c
In file included from gram.y:7725:
scan.l: In function `yyerror':
scan.l:583: warning: int format, different type
Michael Furgal writes:
> We know that the readline support is missing from the psql client.
> It was missing with the cygwin port as well.
You must be using a different cygwin port.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)--
Steve:
We know that the readline support is missing from the psql client.
It was missing with the cygwin port as well. We made little to no
effort to work on the client, our focus was on the server.
We have no plans to add the readline support to the client and
hope that the hacker community wi
On Mon, 8 Oct 2001, Bruce Momjian wrote:
> Are we ready for beta on Wednesday? I don't know anything holding us up
> at this point. Seems like major work has stopped and everyone is ready
> to start testing.
Well, if that build problem I reported doesn't bother you;-)
I think it's likely to
Are we ready for beta on Wednesday? I don't know anything holding us up
at this point. Seems like major work has stopped and everyone is ready
to start testing.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your
...
> OK, can I get another vote for that date.
What was wrong with the 10th? I'm going to be tied up for most of the
time between now and Monday.
- Thomas
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
> > On Thu, 4 Oct 2001, Bruce Momjian wrote:
> >> Can we set a date for beta? If we are at least a week away, we should
> >> say that so people know they can keep working.
>
> I do not think we should slip it yet again, and especially not tell
> people "hey, send in more features", because that
1 - 100 of 345 matches
Mail list logo
