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.
--
Josh
Josh Berkus j...@agliodbs.com 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
On Sat, Aug 07, 2004 at 10:09:22PM -0700, Joe Conway wrote:
listitem
para
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
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
Alvaro Herrera wrote:
Whitespace where?
OK, clarified:
para
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
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
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
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
already
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, did you do a
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
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 exception of
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't have
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
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 was
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't have any great love for
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 be
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.
--
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.
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
...
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
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?
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? :)
Uh,
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
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 at
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. For
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 out of
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 at
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. palloc'd space
-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 works fine. It is a trivial change to the
ADD UNIQUE
code, but it doesn't work. Viewing the system
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 ready
I spent an hour or two trying to get my ADD PRIMARY KEY patch to work but
I'm beginning to think my code is suffering from bit rot. Basically, during
the iteration over the indices on the table, looking for other primary
indices, none are found.
I am checking the indexStruct-indisprimary field,
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 indices as
32 matches
Mail list logo
