Tom Lane writes:
What we could use instead is for someone knowledgeable to commit to
transferring *valid* emailed bug reports into the tracking system.
Bruce could do that if he wants, but there are surely dozens of other
people who would be qualified to handle this task.
I don't think we
I think we should use the best tool available, he is more than willing
to allow open source projects to use it for free.
Dave
On Fri, 2003-11-07 at 23:19, Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Dave Cramer wrote:
Jira is a fantastic bug tracking project management system
Peter Eisentraut [EMAIL PROTECTED] writes:
I don't think we need decicated bug transferrers. Typically, when someone
reports a problem by email, the first step is that some developer or other
expert responds (unless the reporter gets blown away by fellow users as
clueless :-)). So the
http://www.atlassian.com/software/jira/pricing.jsp
I have no particular opinion on whether to use a free or non-free system
to track bugs, but I'd like to recommend RT as being a very capable and
useful program. It has been used to track Perl 5 and CPAN bugs for some
time now, and it happens to
I still think it would be a good idea to have one or two people actively
in charge of the overall health of the bug repository --- cross-linking
duplicate bugs, making sure fixed bugs get closed out, in general
correcting misinformation when they find it. This wouldn't be a large
I think
http://www.atlassian.com/software/jira/pricing.jsp
Another option is free open source Scarab, http://scarab.tigris.org Actually,
I'd prefer it.
__
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
I don't think we need decicated bug transferrers. Typically, when someone
reports a problem by email, the first step is that some developer or other
expert responds (unless the reporter gets blown away by fellow users as
clueless
Once again it's time to consider that old problem that indexes can't
handle cross-datatype comparisons, for example
SELECT ... WHERE int8col = 42
won't use an index on int8col because 42 is int4.
We have spent a huge amount of time trying to find ways to get the system
to assign the same
Tom Lane writes:
Here's what I'm thinking of: specify that the input datatype of an
operator class (pg_opclass.opcintype) is actually just the type of the
indexed column. Operators that are members of the opclass must take this
type as their left-hand input, but the right-hand input can be
Peter Eisentraut [EMAIL PROTECTED] writes:
Tom Lane writes:
One way in which we will lose some flexibility is that this design nails
down forevermore the assumption that the indexed column is on the lefthand
side of any indexable clause.
I don't see this as a problem, but if it becomes one
Bob Ippolito [EMAIL PROTECTED] writes:
On Nov 8, 2003, at 12:31 AM, Tom Lane wrote:
I have just in the past couple hours realized that ps_status.c is
seriously broken on OS X 10.3.
Er... I meant memcmp.. Have you tried removing the system.c hack?
That's what fixed it for me.
AFAICT
On Nov 8, 2003, at 1:13 PM, Tom Lane wrote:
Bob Ippolito [EMAIL PROTECTED] writes:
On Nov 8, 2003, at 12:31 AM, Tom Lane wrote:
I have just in the past couple hours realized that ps_status.c is
seriously broken on OS X 10.3.
Er... I meant memcmp.. Have you tried removing the system.c hack?
Bob Ippolito [EMAIL PROTECTED] writes:
On Nov 8, 2003, at 1:13 PM, Tom Lane wrote:
As for getting rid of system.c, I am not eager to do that since it
would
certainly break compatibility with OS X 10.1. We could conditionally
compile it out perhaps. Do you know what #define symbol we could
On Nov 8, 2003, at 1:44 PM, Tom Lane wrote:
Bob Ippolito [EMAIL PROTECTED] writes:
On Nov 8, 2003, at 1:13 PM, Tom Lane wrote:
As for getting rid of system.c, I am not eager to do that since it
would
certainly break compatibility with OS X 10.1. We could conditionally
compile it out perhaps. Do
I just fixed a bug in ecpglib that caused it to misbehave for all
internal array/vector types. They were treated like the external ones.
So ecpg expected them to be listed as '{...}' which surely failed.
However, this bug fix involves more code changes than I like to just
commit into 7.4 at this
Bob Ippolito [EMAIL PROTECTED] writes:
* I ditched the system.c hack, assuming Apple has fixed them by 10.3 --
because it breaks tcl and python if you do.. I did:
After fixing the ps_status problems, I cannot observe any problem, with
or without system.c. However, I agree that it's a bad
On Nov 8, 2003, at 3:19 PM, Tom Lane wrote:
Bob Ippolito [EMAIL PROTECTED] writes:
* I ditched the system.c hack, assuming Apple has fixed them by 10.3
--
because it breaks tcl and python if you do.. I did:
After fixing the ps_status problems, I cannot observe any problem, with
or without
All,
I'm working on a school project that involves genetic algorithms. We thought
it would be neat to parralelize the genetic algorithm in postgresql's query
optimiser. We used pthreads and are able to spawn threads to deal with the
query optimization, however on exit of the thread the
Hello,
Can you pls explain how the constant values are stored in Postgresql, I
mean using the Const Data Structure.
What does the datum field represent?
Thanks
Shalu
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Christopher Kings-Lynne wrote:
The doesn't quite make the best use of PG quote is one of the best
examples of buck-passing I've seen in awhile. If Bugzilla had been
designed with some thought to DB independence to start with, we'd not
be having this discussion.
You have to laugh at an app
Kurt, this patch added special includes for testing un.h, and I believe
it caused regression failures for the statistics collector. Is it still
needed? What platform is this?
---
Kurt Roeckx wrote:
On Fri, Oct 24, 2003
AgentM,
The treads are joined back together by the master. I did try to debug, but
have to say I hard a hard time with it. I have tried to debug, but didn't
get very far. Debugging Threads is not my forte. :(
Here is the code from :
/src/backend/optimizer/geqo/geqo_main.c
for
On 8 Nov 2003, at 22:19, Tom Lane wrote:
After fixing the ps_status problems, I cannot observe any problem, with
or without system.c. However, I agree that it's a bad idea to
propagate
that hack forward when it's no longer needed. I've #ifdef'd out
system.c for OS X 10.3 and later. (I was
From my SCO contacts re: the failure on OSR5:
I haven't had time and won't have time to fully diagnose this until
after i get back from vacation. In the mean time, i am attaching a
patch which gets OpenServer 5.0.7 to pass 92 of 93 tests with one
test ignored. Basically, this patch just says if
Hi,
I am Suchindra Katageri and am working as a Software Engineer at
Linuxlabs, Atlanta, GA.
I am presently working on developing libraries to make postgresql
run on a cluster. I was wondering if it was possible to force Database
writes to stable storage, without messing up with the
[EMAIL PROTECTED] wrote:
Hi,
I am Suchindra Katageri and am working as a Software Engineer at
Linuxlabs, Atlanta, GA.
I am presently working on developing libraries to make postgresql
run on a cluster. I was wondering if it was possible to force Database
writes to stable storage,
I just tested gcc 2.95.3 on BSD/OS i386 and didn't see any change when
using -g3 vs -g in the size of the binaries.
---
Neil Conway wrote:
On Sat, 2003-10-25 at 21:29, Bruce Momjian wrote:
configure --enable-debug will
Leon Oosterwijk wrote:
All,
I'm working on a school project that involves genetic algorithms. We thought
it would be neat to parralelize the genetic algorithm in postgresql's query
optimiser. We used pthreads and are able to spawn threads to deal with the
query optimization, however on
On Sat, Nov 08, 2003 at 06:36:38PM -0500, Bruce Momjian wrote:
Kurt, this patch added special includes for testing un.h, and I believe
it caused regression failures for the statistics collector. Is it still
needed? What platform is this?
It's a linux system with an (old) libc5. It's still
I guess you are asking how to get the NumericOnly converted to an oid,
and I see from the code that there are very few places where we allow
oid's to be supplied directly. Most oid's come in as part of our
numberic conversion code.
The only idea I have is to call oidin() to do the conversion
Yep. Send patch to patches list and/or have someone who is using this
functionality test it.
---
Michael Meskes wrote:
I just fixed a bug in ecpglib that caused it to misbehave for all
internal array/vector types. They
Is there any way, short of using a debugger with a strategically placed
breakpoint, to tell if a SQL function has been inlined?
Joe
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Joe Conway wrote:
Is there any way, short of using a debugger with a strategically placed
breakpoint, to tell if a SQL function has been inlined?
I think you will only see it with debug_print_plan enabled. You can
change client_min_messages to see that in your psql session. I think
the parse
Bruce Momjian [EMAIL PROTECTED] writes:
I just tested gcc 2.95.3 on BSD/OS i386 and didn't see any change when
using -g3 vs -g in the size of the binaries.
I saw the same with gcc 2.95.3 on HPUX. The gcc manual for this version
does claim that -g3 dumps extra info, but perhaps that is only
Bruce Momjian [EMAIL PROTECTED] writes:
Joe Conway wrote:
Is there any way, short of using a debugger with a strategically placed
breakpoint, to tell if a SQL function has been inlined?
I think you will only see it with debug_print_plan enabled.
If the function is in the WHERE clause then
[EMAIL PROTECTED] writes:
select * from information_schema.tables;
ERROR: unrecognized privilege type: RERERENCES
Replacing the word RERERENCES with REFERENCES in
the predicate has_table_privilege(c.oid,
'RERERENCES'::text) near the end of the view SQL
seems to correct the problem.
Tom Lane wrote:
[EMAIL PROTECTED] writes:
select * from information_schema.tables;
ERROR: unrecognized privilege type: RERERENCES
Replacing the word RERERENCES with REFERENCES in
the predicate has_table_privilege(c.oid,
'RERERENCES'::text) near the end of the view SQL
seems
On Sat, 8 Nov 2003, Tom Lane wrote:
[EMAIL PROTECTED] writes:
select * from information_schema.tables;
ERROR: unrecognized privilege type: RERERENCES
Replacing the word RERERENCES with REFERENCES in
the predicate has_table_privilege(c.oid,
'RERERENCES'::text) near the end of
Marc G. Fournier [EMAIL PROTECTED] writes:
On Sat, 8 Nov 2003, Tom Lane wrote:
I've applied the patch but am loathe to force an initdb this late in
the beta cycle. Any opinions out there?
Annoying as a spelling mistake is (and, from my read of the above, that is
all it is?), I don't thnk it
Marc G. Fournier wrote:
On Sat, 8 Nov 2003, Tom Lane wrote:
[EMAIL PROTECTED] writes:
select * from information_schema.tables;
ERROR: unrecognized privilege type: RERERENCES
Replacing the word RERERENCES with REFERENCES in
the predicate has_table_privilege(c.oid,
Bruce Momjian [EMAIL PROTECTED] writes:
I think we should fix it but not force an initdb ---
information_schema is new and I am not sure how many people are using
it.
Yeah, I'm leaning that way too. We could publicize a script to fix the
problem in any beta5 or RC1 databases that people don't
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I think we should fix it but not force an initdb ---
information_schema is new and I am not sure how many people are using
it.
Yeah, I'm leaning that way too. We could publicize a script to fix the
problem in any beta5 or RC1 databases that
Joe Conway [EMAIL PROTECTED] writes:
I agree, and this brings up a question that I've pondered before. Why do
we ever *require* and initdb when only metadata has changed (i.e. the
contents of the system catalogs, not catalog or page structure)?
In some cases we have to do it because there is
43 matches
Mail list logo
