Lists: | pgsql-hackers |
---|
From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | unresolved bugs |
Date: | 2010-01-06 20:14:47 |
Message-ID: | 603c8f071001061214g45df7639geb0a8567ade50ed6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Over the past few months, I've been attempting to keep tracks of which
postings on pgsql-bugs have not gotten a response and to respond to
those where I have a clue what the issue might be. However, there are
a few that I don't really have an idea about which look like they
might be real bugs... or some of them might be user error, not sure.
The first of these in particular is a fairly detailed report of what
looks might be a fairly serious problem.
pg_listener entries deleted under heavy NOTIFY load only on Windows
http://archives.postgresql.org/pgsql-bugs/2009-12/msg00274.php
COPY staments with paths containing non-ASCII characters under WinXP
http://archives.postgresql.org/pgsql-bugs/2009-12/msg00267.php
BUG #5245: Full Server Certificate Chain Not Sent to client
http://archives.postgresql.org/pgsql-bugs/2009-12/msg00145.php
BUG #5236: Aparent bug in ecpg
http://archives.postgresql.org/pgsql-bugs/2009-12/msg00078.php
incorrect exit code from psql with single transaction + violation of
deferred FK constraint
http://archives.postgresql.org/pgsql-bugs/2009-10/msg00039.php
Should we add any of these here?
http://wiki.postgresql.org/wiki/PostgreSQL_8.5_Open_Items
...Robert
From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-06 20:36:39 |
Message-ID: | 25892.1262810199@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> The first of these in particular is a fairly detailed report of what
> looks might be a fairly serious problem.
> pg_listener entries deleted under heavy NOTIFY load only on Windows
> http://archives.postgresql.org/pgsql-bugs/2009-12/msg00274.php
Yeah, that needs to be looked at by a Windows expert (ie not me).
> COPY staments with paths containing non-ASCII characters under WinXP
> http://archives.postgresql.org/pgsql-bugs/2009-12/msg00267.php
The general question of what to do with non-ASCII paths is still open.
I don't think there's any consensus about what to do about it, mainly
because it's not clear that we know what encoding is in use in the
filesystem. In any case, defining the problem as limited to COPY,
or to Windows, seems to me to be missing the point.
> BUG #5245: Full Server Certificate Chain Not Sent to client
> http://archives.postgresql.org/pgsql-bugs/2009-12/msg00145.php
Not clear to me whether this is a bug, or at least our bug.
Isn't that behavior entirely openssl's to determine?
> BUG #5236: Aparent bug in ecpg
> http://archives.postgresql.org/pgsql-bugs/2009-12/msg00078.php
Michael needs to look at that one.
> incorrect exit code from psql with single transaction + violation of
> deferred FK constraint
> http://archives.postgresql.org/pgsql-bugs/2009-10/msg00039.php
Seems like a bug to me too, or at least dubious.
regards, tom lane
From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-06 21:00:14 |
Message-ID: | 20100106210014.GM6129@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Robert Haas escribió:
> Over the past few months, I've been attempting to keep tracks of which
> postings on pgsql-bugs have not gotten a response and to respond to
> those where I have a clue what the issue might be.
So you installed the bugzilla module on yourself? Neat. Keep at it!
> Should we add any of these here?
>
> http://wiki.postgresql.org/wiki/PostgreSQL_8.5_Open_Items
+1, all of them.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-06 21:04:16 |
Message-ID: | 603c8f071001061304r598f3f32h81c7ce190f8a8bda@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On Wed, Jan 6, 2010 at 4:00 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Robert Haas escribió:
>> Over the past few months, I've been attempting to keep tracks of which
>> postings on pgsql-bugs have not gotten a response and to respond to
>> those where I have a clue what the issue might be.
>
> So you installed the bugzilla module on yourself? Neat. Keep at it!
Actually it's Brucezilla.
...Robert
From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-06 21:10:58 |
Message-ID: | 4B44FC62.30602@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Robert Haas wrote:
> On Wed, Jan 6, 2010 at 4:00 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
>> Robert Haas escribió:
>>> Over the past few months, I've been attempting to keep tracks of which
>>> postings on pgsql-bugs have not gotten a response and to respond to
>>> those where I have a clue what the issue might be.
>> So you installed the bugzilla module on yourself? Neat. Keep at it!
>
> Actually it's Brucezilla.
hmm maybe I should resurrect the bugzilla testbed again :)
Stefan
From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-06 21:30:53 |
Message-ID: | 603c8f071001061330y5b3f918yb718fc638658611b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On Wed, Jan 6, 2010 at 4:10 PM, Stefan Kaltenbrunner
<stefan(at)kaltenbrunner(dot)cc> wrote:
> Robert Haas wrote:
>>
>> On Wed, Jan 6, 2010 at 4:00 PM, Alvaro Herrera
>> <alvherre(at)commandprompt(dot)com> wrote:
>>>
>>> Robert Haas escribió:
>>>>
>>>> Over the past few months, I've been attempting to keep tracks of which
>>>> postings on pgsql-bugs have not gotten a response and to respond to
>>>> those where I have a clue what the issue might be.
>>>
>>> So you installed the bugzilla module on yourself? Neat. Keep at it!
>>
>> Actually it's Brucezilla.
>
> hmm maybe I should resurrect the bugzilla testbed again :)
If we're going to use a bug-tracker, Bugzilla wouldn't be my first
choice, I don't think. Honestly what I'd like better than a
full-fledged trackers is just a webapp that lists all the unreplied-to
emails in the pgsql-bugs archives. That wouldn't of course tell you
if a bug got a reply that didn't actually resolve the issue, but that
doesn't seem to be very common anyway. Most times if nobody responds
it's because either (1) it's not really a bug (user question, feature
request, etc.) or (2) the person who is qualified to respond doesn't
actually read pgsql-bugs.
...Robert
From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-06 21:35:12 |
Message-ID: | 20100106213512.GN6129@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Robert Haas escribió:
> On Wed, Jan 6, 2010 at 4:10 PM, Stefan Kaltenbrunner
> <stefan(at)kaltenbrunner(dot)cc> wrote:
> > hmm maybe I should resurrect the bugzilla testbed again :)
>
> If we're going to use a bug-tracker, Bugzilla wouldn't be my first
> choice, I don't think. Honestly what I'd like better than a
> full-fledged trackers is just a webapp that lists all the unreplied-to
> emails in the pgsql-bugs archives.
Hey, let's use debbugs!
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-06 22:08:04 |
Message-ID: | m23a2isx8b.fsf@hi-media.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> If we're going to use a bug-tracker, Bugzilla wouldn't be my first
> choice, I don't think. Honestly what I'd like better than a
> full-fledged trackers is just a webapp that lists all the unreplied-to
> emails in the pgsql-bugs archives.
For something like a flexible archiving solution of mails, what about
having a look at ArchiveOpteryx, which offers IMAP service atop a
PostgreSQL database containing emails, along with full text search and
virtual search folders. And a web interface too.
http://www.archiveopteryx.org/
http://archives.aox.org/archives/pgsql-announce
I don't know the details because I'm yet to operate that, but it seems
like it could help us.
Regards,
--
dim
From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-06 23:09:32 |
Message-ID: | 4B45182C.3000508@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Robert Haas escribió:
>
>> On Wed, Jan 6, 2010 at 4:10 PM, Stefan Kaltenbrunner
>> <stefan(at)kaltenbrunner(dot)cc> wrote:
>>
>
>
>>> hmm maybe I should resurrect the bugzilla testbed again :)
>>>
>> If we're going to use a bug-tracker, Bugzilla wouldn't be my first
>> choice, I don't think. Honestly what I'd like better than a
>> full-fledged trackers is just a webapp that lists all the unreplied-to
>> emails in the pgsql-bugs archives.
>>
>
> Hey, let's use debbugs!
>
Oh, wow, I didn't realize it was time for another round of this. Wheeeee!
cheers
andrew
From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 00:40:30 |
Message-ID: | 603c8f071001061640m5d6fd8cbw4351e3d2604c658c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On Wed, Jan 6, 2010 at 6:09 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Alvaro Herrera wrote:
>> Robert Haas escribió:
>>> On Wed, Jan 6, 2010 at 4:10 PM, Stefan Kaltenbrunner
>>> <stefan(at)kaltenbrunner(dot)cc> wrote:
>>>> hmm maybe I should resurrect the bugzilla testbed again :)
>>> If we're going to use a bug-tracker, Bugzilla wouldn't be my first
>>> choice, I don't think. Honestly what I'd like better than a
>>> full-fledged trackers is just a webapp that lists all the unreplied-to
>>> emails in the pgsql-bugs archives.
>> Hey, let's use debbugs!
> Oh, wow, I didn't realize it was time for another round of this. Wheeeee!
Personally, I was more hoping we could consider fixing some of them...
...Robert
From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 00:44:44 |
Message-ID: | 4B452E7C.9050306@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
> Personally, I was more hoping we could consider fixing some of them...
Agreed. I really don't think a bug tracker helps us. We need two things:
(1) to respond to bug submissions immediately and fix them, and
(2) if we can't fix the bugs immediately, to add them to a TODO list
Adding stuff to a bug tracker is just a way to procrastinate on it
indefinitely.
--Josh Berkus
From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 00:45:04 |
Message-ID: | 407d949e1001061645n4c067040y6e284c1c2eb61f2e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On Wed, Jan 6, 2010 at 11:09 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Oh, wow, I didn't realize it was time for another round of this. Wheeeee!
>
Actually I suspect it is time.
My preferences have changed. While they used to go something like
debbugs > RT > nothing > bugzilla they now go something like debbugs >
RT > bugzilla > nothing. That is, even though bugzilla is possibly my
least favourite open source bug tracking system it's still better than
continuing the way we are. We've been pretty lucky so far, in part due
to Tom and others being remarkably diligent but it's only a matter of
time until we forget or miss a critical report. And from a PR point of
view it just looks terrible.
So in short while I still think debbugs is the best approach to this
I've seen at this point *any* free software based solution is fine
with me.
I'm assuming they can all be configured to send all new bug reports to
a mailing list and I do think we should choose one that stores the
database in Postgres, but I think that's true for nearly all of them
and can be made true for all of them.
--
greg
From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 00:52:07 |
Message-ID: | 1262825527.8287.415.camel@jd-desktop.unknown.charter.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On Thu, 2010-01-07 at 00:45 +0000, Greg Stark wrote:
> On Wed, Jan 6, 2010 at 11:09 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> > Oh, wow, I didn't realize it was time for another round of this. Wheeeee!
> >
>
> Actually I suspect it is time.
>
> My preferences have changed. While they used to go something like
> debbugs > RT > nothing > bugzilla they now go something like debbugs >
> RT > bugzilla > nothing. That is, even though bugzilla is possibly my
> least favourite open source bug tracking system it's still better than
> continuing the way we are. We've been pretty lucky so far, in part due
> to Tom and others being remarkably diligent but it's only a matter of
> time until we forget or miss a critical report. And from a PR point of
> view it just looks terrible.
>
> So in short while I still think debbugs is the best approach to this
> I've seen at this point *any* free software based solution is fine
> with me.
I have been looking at roundup fairly extensively. It is what
bugs.python.org uses.
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir.
From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 00:55:46 |
Message-ID: | 407d949e1001061655q304bff94nd6762190659ef462@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On Thu, Jan 7, 2010 at 12:44 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Agreed. I really don't think a bug tracker helps us. We need two things:
>
> (1) to respond to bug submissions immediately and fix them, and
> (2) if we can't fix the bugs immediately, to add them to a TODO list
>
> Adding stuff to a bug tracker is just a way to procrastinate on it
> indefinitely.
>
It's up to us what issues we want to track in what system. It's
perfectly acceptable to say any todo items are tracked outside in the
TODO wiki page. And incidentally I agree with you.
But we also have the open items list that Bruce (sorry I should have
credited you before) and Tom and now apparently Robert track. These
issues are usually tracked for the current development tree because
we're more willing to leave these pending in the development tree but
they also come up for point releases. Sometimes we're not sure what
the right fix is right away or we're waiting on some research or
debugging work but they have to be taken care of for the next release
or declared non-bugs or not worth fixing. They shouldn't just be
forgotten about.
So far we've done a good job but it would be more credible for people
not following the lists if we could point them at the current list at
any time and see what kind of known issues we have and what happens to
issues they report.
--
greg
From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 01:06:35 |
Message-ID: | 4B45339B.5000807@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Greg Stark wrote:
> On Thu, Jan 7, 2010 at 12:44 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>> Agreed. I really don't think a bug tracker helps us. We need two things:
>>
>> (1) to respond to bug submissions immediately and fix them, and
>> (2) if we can't fix the bugs immediately, to add them to a TODO list
>>
>> Adding stuff to a bug tracker is just a way to procrastinate on it
>> indefinitely.
>>
>>
>
> It's up to us what issues we want to track in what system. It's
> perfectly acceptable to say any todo items are tracked outside in the
> TODO wiki page. And incidentally I agree with you.
>
> But we also have the open items list that Bruce (sorry I should have
> credited you before) and Tom and now apparently Robert track. These
> issues are usually tracked for the current development tree because
> we're more willing to leave these pending in the development tree but
> they also come up for point releases. Sometimes we're not sure what
> the right fix is right away or we're waiting on some research or
> debugging work but they have to be taken care of for the next release
> or declared non-bugs or not worth fixing. They shouldn't just be
> forgotten about.
>
> So far we've done a good job but it would be more credible for people
> not following the lists if we could point them at the current list at
> any time and see what kind of known issues we have and what happens to
> issues they report.
>
I think the commitfest app has actually given us a handle on how we
could use a tracker. (Kudos to Robert for that app, btw). People feared
that it would become an alternative to the mailing list(s), but it
hasn't in practice. people have expressed the same fear abotu a tracker,
but presumably we could use a tracker in a similar fashion.
It really would be nice for users to be able to search for bugs, and see
where/when_ot_if/how they got resolved, without having to seach mailing
list archives.
Stefan did some terrific work a couple of years ago to marry up bugzilla
to the -bugs mailing list and web forms, before we ran out of steam.
cheers
andrew
From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 06:40:54 |
Message-ID: | 1262846454.14688.15.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On ons, 2010-01-06 at 16:44 -0800, Josh Berkus wrote:
> > Personally, I was more hoping we could consider fixing some of them...
>
> Agreed. I really don't think a bug tracker helps us. We need two things:
>
> (1) to respond to bug submissions immediately and fix them, and
> (2) if we can't fix the bugs immediately, to add them to a TODO list
>
> Adding stuff to a bug tracker is just a way to procrastinate on it
> indefinitely.
The problem is that your two-step plan requires failsafe human
intervention, whereas a bug tracker doesn't.
From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 07:54:34 |
Message-ID: | 4B45933A.8030203@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Robert Haas wrote:
> On Wed, Jan 6, 2010 at 4:10 PM, Stefan Kaltenbrunner
> <stefan(at)kaltenbrunner(dot)cc> wrote:
>> Robert Haas wrote:
>>> On Wed, Jan 6, 2010 at 4:00 PM, Alvaro Herrera
>>> <alvherre(at)commandprompt(dot)com> wrote:
>>>> Robert Haas escribió:
>>>>> Over the past few months, I've been attempting to keep tracks of which
>>>>> postings on pgsql-bugs have not gotten a response and to respond to
>>>>> those where I have a clue what the issue might be.
>>>> So you installed the bugzilla module on yourself? Neat. Keep at it!
>>> Actually it's Brucezilla.
>> hmm maybe I should resurrect the bugzilla testbed again :)
>
> If we're going to use a bug-tracker, Bugzilla wouldn't be my first
> choice, I don't think. Honestly what I'd like better than a
> full-fledged trackers is just a webapp that lists all the unreplied-to
> emails in the pgsql-bugs archives. That wouldn't of course tell you
> if a bug got a reply that didn't actually resolve the issue, but that
> doesn't seem to be very common anyway. Most times if nobody responds
> it's because either (1) it's not really a bug (user question, feature
> request, etc.) or (2) the person who is qualified to respond doesn't
> actually read pgsql-bugs.
*sigh* - that was mostly ment as a joke and not a really serious
comment. However the idea I actually had with BZ back in the days was
not to use it as a full fledged tracker(in the sense of exposing it to
users or developers)
Instead I would just use it as the background engine that does nothing
more than being subscribed to -bugs, tracks the stuff there and provides
an summary export about (not)replied to reports. If somebody later on
wants to annotate the emails/reports there (as in solved,open,moved to
todo,not a pg core question,whatever) fine - if not fine as well :)
Stefan
From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 10:10:52 |
Message-ID: | 20100107101052.GA10831@feivel.credativ.lan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On Wed, Jan 06, 2010 at 03:36:39PM -0500, Tom Lane wrote:
> > BUG #5236: Aparent bug in ecpg
> > http://archives.postgresql.org/pgsql-bugs/2009-12/msg00078.php
>
> Michael needs to look at that one.
I'm waiting for a reproducable test case.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo/Skype: michaelmeskes, Jabber: meskes(at)jabber(dot)org
VfL Borussia! Forca Barca! Go SF 49ers! Use: Debian GNU/Linux, PostgreSQL
From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 13:10:36 |
Message-ID: | 21026.1262869836@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> *sigh* - that was mostly ment as a joke and not a really serious
> comment. However the idea I actually had with BZ back in the days was
> not to use it as a full fledged tracker(in the sense of exposing it to
> users or developers)
> Instead I would just use it as the background engine that does nothing
> more than being subscribed to -bugs, tracks the stuff there and provides
> an summary export about (not)replied to reports. If somebody later on
> wants to annotate the emails/reports there (as in solved,open,moved to
> todo,not a pg core question,whatever) fine - if not fine as well :)
bugzilla doesn't really interface to email well enough to do that.
I gather that debbugs might work better, but I have no personal
experience with it.
regards, tom lane
From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 14:05:09 |
Message-ID: | 4B45EA15.1030200@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
> bugzilla doesn't really interface to email well enough to do that.
> I gather that debbugs might work better, but I have no personal
> experience with it.
>
>
1. My recollection is that last time we looked the debbugs people
themselves said they didn't think it was suitable for us.
2. IIRC there are at least some facilities (possibly using extra
modules) for bugzilla <-> email integration. I haven't looked at it
lately, however, so I don't know what the state of play is. I think
Stefan got some good stuff working a couple of years ago.
cheers
andrew
From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 14:19:44 |
Message-ID: | 4B45ED80.8060808@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>> *sigh* - that was mostly ment as a joke and not a really serious
>> comment. However the idea I actually had with BZ back in the days was
>> not to use it as a full fledged tracker(in the sense of exposing it to
>> users or developers)
>> Instead I would just use it as the background engine that does nothing
>> more than being subscribed to -bugs, tracks the stuff there and provides
>> an summary export about (not)replied to reports. If somebody later on
>> wants to annotate the emails/reports there (as in solved,open,moved to
>> todo,not a pg core question,whatever) fine - if not fine as well :)
>
> bugzilla doesn't really interface to email well enough to do that.
> I gather that debbugs might work better, but I have no personal
> experience with it.
well recent bugzilla versions do have both an email interface (an early
version of that was used in my prototype - the newer ones are much more
powerful an can do) and an remote XML-RPC Interface (which I used for
the bugform integration).
As a pure email tracker with no real external apps debbugs is probably
more powerful though (but not really used a lot outside of the debian
project).
Stefan
From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 15:55:11 |
Message-ID: | 9837222c1001070755g1e68507bu28ed16a3de2b6cf1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On Wed, Jan 6, 2010 at 21:36, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> The first of these in particular is a fairly detailed report of what
>> looks might be a fairly serious problem.
>
>> pg_listener entries deleted under heavy NOTIFY load only on Windows
>> http://archives.postgresql.org/pgsql-bugs/2009-12/msg00274.php
>
> Yeah, that needs to be looked at by a Windows expert (ie not me).
I missed that one. Will add to my list.
>> BUG #5245: Full Server Certificate Chain Not Sent to client
>> http://archives.postgresql.org/pgsql-bugs/2009-12/msg00145.php
>
> Not clear to me whether this is a bug, or at least our bug.
It's not a bug, it's potentially a feature request :)
> Isn't that behavior entirely openssl's to determine?
No, I think we can control that somehow.
Let's leave it on the open items list, and I'll try to find some time
to investigate it. Since it's behavior change, it's probably 8.5
material, and not backpatch. Oh, and if somebody else has the time to
investigate it, please be my guest :)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unresolved bugs |
Date: | 2010-01-07 19:13:35 |
Message-ID: | 4B46325F.7090107@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
> 1. My recollection is that last time we looked the debbugs people
> themselves said they didn't think it was suitable for us.
You recall correctly. This was a discussion with some of the debbugs
maintainers 2 years ago.
--Josh Berkus
From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: unresolved bugs |
Date: | 2010-04-20 00:31:00 |
Message-ID: | n2w603c8f071004191731sb7360120z2e3670f21c4bdbd6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On Thu, Jan 7, 2010 at 11:55 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>> BUG #5245: Full Server Certificate Chain Not Sent to client
>>> http://archives.postgresql.org/pgsql-bugs/2009-12/msg00145.php
>>
>> Not clear to me whether this is a bug, or at least our bug.
>
> It's not a bug, it's potentially a feature request :)
>
>> Isn't that behavior entirely openssl's to determine?
>
> No, I think we can control that somehow.
>
> Let's leave it on the open items list, and I'll try to find some time
> to investigate it. Since it's behavior change, it's probably 8.5
> material, and not backpatch. Oh, and if somebody else has the time to
> investigate it, please be my guest :)
Magnus told me on IM today that he feels this should be reclassified
as a Todo, so I'm going to move it there from open items.
...Robert