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:
> >>
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
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, 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
> 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 will lead to
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.
If we say the 10th I won't have to change the developer's page :)
Vince.
--
===
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.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Aven
> Marc G. Fournier writes:
>
> > with all the changes going on, we're most likely looking at Oct 1st,
> > earliest ... things are startin to stabilize, but until that 18gig is
> > installed next week, we still have th eproblems with updating ftp, unless
> > Peter can clear out th e400+Meg in his
Marc G. Fournier writes:
> with all the changes going on, we're most likely looking at Oct 1st,
> earliest ... things are startin to stabilize, but until that 18gig is
> installed next week, we still have th eproblems with updating ftp, unless
> Peter can clear out th e400+Meg in his acount? :)
with all the changes going on, we're most likely looking at Oct 1st,
earliest ... things are startin to stabilize, but until that 18gig is
installed next week, we still have th eproblems with updating ftp, unless
Peter can clear out th e400+Meg in his acount? :)
On Sun, 23 Sep 2001, Bruce Momjia
I know we had expected beta last Friday, but I think the needed CVS
changes have delayed that. I know a few people are working on final
additions. Perhaps this Friday would be a good beta target.
Tom and I will be at the OSDN conference until Wednesday.
--
Bruce Momjian
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> I'd suggest issuing the NOTICE inside the loop, actually,
>> and not breaking at all. (See also #4)
> I don't quite understand what you mean here?
Just do elog(NOTICE) inside the loop over indexes, rather than setting a
flag to do it later.
> 1. Should not "break" out of loop over indexes after detecting a
> matching non-primary-key index. This allows detection of the NOTICE
> condition to distract you from detecting the ERROR condition on a
> later index. I'd suggest issuing the NOTICE inside the loop, actually,
> and not breaking
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> 3. pfree'ing iname at the bottom doesn't strike me as a good
>> idea; isn't that possibly part of your input querytree?
> Hmmm. OK. What about in the case where iname is null and I give it a
> makeObjectName?
Don't worry about it. pallo
> 1. Should not "break" out of loop over indexes after detecting a
> matching non-primary-key index. This allows detection of the NOTICE
> condition to distract you from detecting the ERROR condition on a
> later index. I'd suggest issuing the NOTICE inside the loop, actually,
> and not breaking
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Attached is the CONSTR_PRIMARY switch block from command.c. I've marked the
> problem test with '@@'.
Hmmm this code has got a number of problems, but I don't see why
*that* would fail. Anyone?
What I do see:
1. Should not "break" o
> Cc: Bruce Momjian; PostgreSQL-development
> Subject: Re: [HACKERS] Beta time
>
>
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> > I am checking the indexStruct->indisprimary field, but it
> always resolves to
> > false. indisunique work
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> I am checking the indexStruct->indisprimary field, but it always resolves to
> false. indisunique works fine. It is a trivial change to the ADD UNIQUE
> code, but it doesn't work. Viewing the system catalogs and '\d' both show
> the indice
IL PROTECTED]]On Behalf Of Bruce Momjian
> Sent: Tuesday, 18 September 2001 12:00 AM
> To: PostgreSQL-development
> Subject: [HACKERS] Beta time
>
>
> I want to mention that the number of patches submitted has dropped off
> dramatically. Seems people are prepared for beta and w
> I want to mention that the number of patches submitted has dropped off
> dramatically. Seems people are prepared for beta and we should start
> beta as soon as we can. I think the current plan is Friday.
I'm doing a substantial amount of work on the date/time types. Not
certain it will be rea
I want to mention that the number of patches submitted has dropped off
dramatically. Seems people are prepared for beta and we should start
beta as soon as we can. I think the current plan is Friday.
Also, I will be on vacation this week. Tom will apply any patches that
look good.
--
Bruce
39 matches
Mail list logo
