Re: [BUGS] bugs that have not been replied-to on list

2010-04-28 Thread Robert Haas
On Wed, Apr 28, 2010 at 4:09 PM, Dimitri Fontaine wrote: > Stefan Kaltenbrunner writes: >> As in have a (hyptothetical) tracker being subscribed to -bugs (and maybe >> the other lists in the future as well) so the workflow would look like >> this: > > Well there is a WIP to use an ArchiveOpteryX

Re: [BUGS] bugs that have not been replied-to on list

2010-04-28 Thread Dimitri Fontaine
Stefan Kaltenbrunner writes: > As in have a (hyptothetical) tracker being subscribed to -bugs (and maybe > the other lists in the future as well) so the workflow would look like > this: Well there is a WIP to use an ArchiveOpteryX based solution to replace the archives and get rid of the artifici

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Peter Eisentraut
On mån, 2010-04-19 at 15:37 -0400, Robert Haas wrote: > As far as I am concerned, this is just bellyaching. I'm glad Tom > fixes most of the bugs because otherwise we would have a lot more > unfixed bugs. But he's not from the only one who responds to bug > reports, and we seem to have a pretty g

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Robert Haas
On Mon, Apr 19, 2010 at 5:02 AM, Peter Eisentraut wrote: > On mån, 2010-04-19 at 09:59 +0200, Stefan Kaltenbrunner wrote: >> I think we would not even need to expose the webinterface to the wider >> community, what we probably want is something that let's us keep the >> current workflow but provid

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Robert Haas
On Mon, Apr 19, 2010 at 11:55 AM, Kevin Grittner wrote: > Tom Lane wrote: > >> IME many of the bugs that go unanswered are non-bugs (eg #5316) >> or inadequately described (eg #5429) > > Agreed. > >> If the goal is "make sure nothing important slips through the >> cracks", a tracker could help.  

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Kevin Grittner
Tom Lane wrote: > IME many of the bugs that go unanswered are non-bugs (eg #5316) > or inadequately described (eg #5429) Agreed. > If the goal is "make sure nothing important slips through the > cracks", a tracker could help. If the goal is "100% response rate > to pgsql-bugs submissions",

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Tom Lane
Jaime Casanova writes: > On Sun, Apr 18, 2010 at 9:03 PM, Robert Haas wrote: >> What is frustrating about the current process is that ~5% of the bugs don't >> get a response.  How are we going to fix that problem? > that's a two side problem, while certainly there are valid bug reports > that f

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Andy Balholm
Despite all the problems with PostgreSQL's bug-tracking system or non-system, I've found it much nicer to deal with than OpenOffice's. I really like the fact that it's e-mail based rather than web based. Part of the reason for that is that I have e-mail but not web access, so I can deal with it

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Peter Eisentraut
On mån, 2010-04-19 at 09:59 +0200, Stefan Kaltenbrunner wrote: > I think we would not even need to expose the webinterface to the wider > community, what we probably want is something that let's us keep the > current workflow but provides a minimalistic > status/statistics/dashboard > feature on

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Peter Eisentraut
On sön, 2010-04-18 at 19:47 +, Greg Sabino Mullane wrote: > > That all sounds pretty reasonable to me, though I would favor using > > something other than Bugzilla for the tracker. I'm not really sure if > > there's anything that I'd consider truly good out there, but I've > > always found Bug

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Craig Ringer
Stefan Kaltenbrunner wrote: > 2a. we can simply have the tracker export a dashboard status of: > > *) stuff that had no reply too (which is one of the open questions) > *) if a commit has the bug id we could have it autoclose/autotrack that > as well > > 2b. for the case of "not a bug"/"added to

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Craig Ringer
Stefan Kaltenbrunner wrote: > by nagging people - if we simply had a dashboard or an email interface > (think of the buildfarm dashboard and the status email reports it > provides to both developers and animalowners) to make the issue more > visible I think most of the problem of "no reply at all"

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Stefan Kaltenbrunner
Robert Haas wrote: On Sun, Apr 18, 2010 at 5:29 PM, Magnus Hagander wrote: On Sun, Apr 18, 2010 at 23:14, Tom Lane wrote: Jaime Casanova writes: On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas wrote: On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane wrote: Bugzilla is the worst form of

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Stefan Kaltenbrunner
Tom Lane wrote: Jaime Casanova writes: On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas wrote: On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane wrote: Bugzilla is the worst form of bug tracking out there, except for all the others. One of these days, I am going to write a @$#! bug tracker.

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Stefan Kaltenbrunner
Robert Haas wrote: On Sun, Apr 11, 2010 at 7:14 AM, Stefan Kaltenbrunner wrote: Jasen Betts wrote: On 2010-04-10, Stefan Kaltenbrunner wrote: Craig Ringer wrote: Dave Page wrote: This basically indicates that we need an issue tracker. There, look - now see what you made me do :-( Please?

Re: [BUGS] bugs that have not been replied-to on list

2010-04-18 Thread Jaime Casanova
On Sun, Apr 18, 2010 at 9:03 PM, Robert Haas wrote: [...] > What is frustrating about the current process is that ~5% of the bugs don't > get a response.  How are we going to fix that problem? > that's a two side problem, while certainly there are valid bug reports that fall in the cracks, there

Re: [BUGS] bugs that have not been replied-to on list

2010-04-18 Thread Robert Haas
On Sun, Apr 18, 2010 at 5:29 PM, Magnus Hagander wrote: > On Sun, Apr 18, 2010 at 23:14, Tom Lane wrote: >> Jaime Casanova writes: >>> On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas wrote: On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane wrote: > Bugzilla is the worst form of

Re: [BUGS] bugs that have not been replied-to on list

2010-04-18 Thread John R Pierce
Greg Sabino Mullane wrote: Bugzilla is the worst form of bug tracking out there, except for all the others. flyspray isn't half bad, especially because its really simple and fairly clean. supports pgsql too. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make chang

Re: [BUGS] bugs that have not been replied-to on list

2010-04-18 Thread Magnus Hagander
On Sun, Apr 18, 2010 at 23:14, Tom Lane wrote: > Jaime Casanova writes: >> On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas wrote: >>> On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane >>> wrote: Bugzilla is the worst form of bug tracking out there, except for all the others. >>> >>>

Re: [BUGS] bugs that have not been replied-to on list

2010-04-18 Thread Tom Lane
Jaime Casanova writes: > On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas wrote: >> On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane >> wrote: >>> Bugzilla is the worst form of bug tracking out there, except for >>> all the others. >> >> One of these days, I am going to write a @$#! bug tracke

Re: [BUGS] bugs that have not been replied-to on list

2010-04-18 Thread Jaime Casanova
On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas wrote: > On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane > wrote: >>> That all sounds pretty reasonable to me, though I would favor using >>> something other than Bugzilla for the tracker.  I'm not really sure if >>> there's anything that I'd con

Re: [BUGS] bugs that have not been replied-to on list

2010-04-18 Thread Robert Haas
On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane wrote: >> That all sounds pretty reasonable to me, though I would favor using >> something other than Bugzilla for the tracker.  I'm not really sure if >> there's anything that I'd consider truly good out there, but I've >> always found Bugzilla

Re: [BUGS] bugs that have not been replied-to on list

2010-04-18 Thread Greg Sabino Mullane
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 > That all sounds pretty reasonable to me, though I would favor using > something other than Bugzilla for the tracker. I'm not really sure if > there's anything that I'd consider truly good out there, but I've > always found Bugzilla pretty ter

Re: [BUGS] bugs that have not been replied-to on list

2010-04-18 Thread Peter Eisentraut
On sön, 2010-04-18 at 13:12 -0400, Robert Haas wrote: > That all sounds pretty reasonable to me, though I would favor using > something other than Bugzilla for the tracker. I'm not really sure if > there's anything that I'd consider truly good out there, There isn't. Welcome to the show. ;-)

Re: [BUGS] bugs that have not been replied-to on list

2010-04-18 Thread Robert Haas
On Sun, Apr 11, 2010 at 7:14 AM, Stefan Kaltenbrunner wrote: > Jasen Betts wrote: >> >> On 2010-04-10, Stefan Kaltenbrunner wrote: >>> >>> Craig Ringer wrote: Dave Page wrote: > This basically indicates that we need an issue tracker. There, look - > now see what you made me

Re: [BUGS] bugs that have not been replied-to on list

2010-04-11 Thread Stefan Kaltenbrunner
Jasen Betts wrote: On 2010-04-10, Stefan Kaltenbrunner wrote: Craig Ringer wrote: Dave Page wrote: This basically indicates that we need an issue tracker. There, look - now see what you made me do :-( Please?!? I wonder, if EDB just went ahead and set one up, would people start using it? I

Re: [BUGS] bugs that have not been replied-to on list

2010-04-11 Thread Jasen Betts
On 2010-04-10, Stefan Kaltenbrunner wrote: > Craig Ringer wrote: >> Dave Page wrote: >> >>> This basically indicates that we need an issue tracker. There, look - >>> now see what you made me do :-( >> >> Please?!? >> >> I wonder, if EDB just went ahead and set one up, would people start >> usin

Re: [BUGS] bugs that have not been replied-to on list

2010-04-10 Thread Stefan Kaltenbrunner
Craig Ringer wrote: Dave Page wrote: This basically indicates that we need an issue tracker. There, look - now see what you made me do :-( Please?!? I wonder, if EDB just went ahead and set one up, would people start using it? I've been tempted to do it myself, but I'm not confident I can ha

Re: [BUGS] bugs that have not been replied-to on list

2010-04-10 Thread Craig Ringer
Dave Page wrote: > This basically indicates that we need an issue tracker. There, look - > now see what you made me do :-( Please?!? I wonder, if EDB just went ahead and set one up, would people start using it? I've been tempted to do it myself, but I'm not confident I can handle the bandwidth/h

Re: [BUGS] bugs that have not been replied-to on list

2010-04-10 Thread Craig Ringer
Andy Balholm wrote: > On Apr 9, 2010, at 5:08 AM, Robert Haas wrote: > >> Something is wrong with this >> mailing list. > > In the week and a half that I've been subscribed to this mailing > list, there have been several times that I received a reply to a > message without receiving the origina

Re: [BUGS] bugs that have not been replied-to on list

2010-04-09 Thread Kevin Grittner
Andy Balholm wrote: > On Apr 9, 2010, at 5:08 AM, Robert Haas wrote: > >> Something is wrong with this mailing list. > > In the week and a half that I've been subscribed to this mailing > list, there have been several times that I received a reply to a > message without receiving the original

Re: [BUGS] bugs that have not been replied-to on list

2010-04-09 Thread Andy Balholm
On Apr 9, 2010, at 5:08 AM, Robert Haas wrote: > Something is wrong with this > mailing list. In the week and a half that I've been subscribed to this mailing list, there have been several times that I received a reply to a message without receiving the original message. In most cases, I rece

Re: [BUGS] bugs that have not been replied-to on list

2010-04-09 Thread Robert Haas
On Fri, Apr 9, 2010 at 4:43 AM, Dave Page wrote: > On Thu, Apr 8, 2010 at 10:23 PM, Robert Haas wrote: > >> BUG #5287: ispell dict erroneously returns lexeme on all prefix+suffix >> cross products >> BUG #5300: Bug on Mac OS X 10.6 and Postgres 8.4 >> BUG #5316: not handled error in inherit queri

Re: [BUGS] bugs that have not been replied-to on list

2010-04-09 Thread Dave Page
On Thu, Apr 8, 2010 at 10:23 PM, Robert Haas wrote: > BUG #5287: ispell dict erroneously returns lexeme on all prefix+suffix > cross products > BUG #5300: Bug on Mac OS X 10.6 and Postgres 8.4 > BUG #5316: not handled error in inherit queries > BUG #5335: GUC value lost on exception > BUG #4785:

Re: [BUGS] Bugs

2008-01-29 Thread Gregory Stark
"Abhay Kumar" <[EMAIL PROTECTED]> writes: > Hi, > I am installing the Postgis 2.2.1 on PostgreSQL. I think you would be better off speaking to this mailing list: http://postgis.refractions.net/mailman/listinfo/postgis-users -- Gregory Stark EnterpriseDB http://www.enterprise

Re: [BUGS] {BUGS] BUG #3110: Online Backup introduces Duplicate OIDs

2007-03-08 Thread Randy Isbell
> Question for Randy -- is this plain PostgreSQL, or are you using some, > hmmm, proprietary derivate of it? Good question, but this is the plain vanilla version of 8.2.3. My latest intel says the proprietary derivative in not currently available at 8.2.3. - r. Randy Isbell Technical Lead

Re: [BUGS] BUGs for function returning a SETOF values on linux postgres 8.0.4, the same function runs correctly on win postgres 8.1

2005-12-01 Thread Michael Fuhr
On Wed, Nov 30, 2005 at 02:53:44PM -0700, Susan Fu wrote: > I am trying to run a very simple test on the above version. This test > works fine on my window 8.1 version. > If I am taking out the function on the 8.0.4 version on linux as just > the select (SELECT DISTINCT value FROM colors) I can see

Re: [BUGS] BUGs for function returning a SETOF values on linux postgres 8.0.4, the same function runs correctly on win postgres 8.1

2005-12-01 Thread Tom Lane
"Susan Fu" <[EMAIL PROTECTED]> writes: > Failed to execute SQL : SQL select * from tt(); failed : ERROR: control = > reached end of function without RETURN CONTEXT: PL/pgSQL function "tt" This is not a bug. 8.0 requires a RETURN in all cases. 8.1 is laxer about it. rega

Re: [BUGS] BUGS

2005-05-22 Thread Jaime Casanova
On 5/21/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > i am trying to get some help around this, i couldnt find anywhere not on > cygwin.com or anywhere else and i also saw that many others have the same > problem on forums but no replies. please help : > thanks in advance > > > creating con

Re: [BUGS] Bugs in bigint indexes

2003-12-19 Thread jmm
Title: Message Try this    explain SELECT id FROM it_test WHERE id='123'; QUERY PLAN Index Scan using it_test_pkey on it_test  (cost=0.00..4.82 rows=1 width=8)   Index Cond: (id = 123

Re: [BUGS] Bugs in bigint indexes

2003-12-19 Thread Tom Lane
Nishad Prakash <[EMAIL PROTECTED]> writes: > Why doesn't the query planner notice that an int-type index is present > and perform the cast on its own? Perhaps one of the developers > can explain? I think users would like this property if it could be > implemented without breaking anything. It's

Re: [BUGS] Bugs in bigint indexes

2003-12-19 Thread Nishad Prakash
On Wed, 17 Dec 2003, Gustavo Scotti wrote: > > _ > > > Dear developers, > > I almost got nuts those two days I'm stuck with this issue... > Let's get straight to the point. I'm using a small portion of my actual > table, but this is enough.

Re: [BUGS] Bugs in bigint indexes

2003-12-19 Thread Peter Eisentraut
Gustavo Scotti writes: > when the key is bigint, it ignores any kind of index scan, it always use > Seq scan. Why? RTFM: http://www.postgresql.org/docs/7.4/static/datatype.html#DATATYPE-INT Please don't post to pgsql-bugs unless you have found a bug. ---(end of broadcast

Re: [BUGS] Bugs or Error?

2003-03-19 Thread Tom Lane
Ninonard Policarpio <[EMAIL PROTECTED]> writes: > What i did is i install the postgresql 7.2.1mlx for libs, posgresql, and > server What in the world is "postgresql 7.2.1mlx" ? > "NOTICE: write error may be permanent: cannot write block 10 for 22892/1249 > ERROR: cannot write block 10 of 22892

Re: [BUGS] Bugs with rules on views/tables: permission denied

2003-02-24 Thread Donald Fraser
  - Original Message - From: "Tom Lane" <[EMAIL PROTECTED]> To: "Donald Fraser" <[EMAIL PROTECTED]> Cc: "[BUGS]" <[EMAIL PROTECTED]> Sent: Monday, February 24, 2003 8:29 PM Subject: Re: [BUGS] Bugs with rules on views/tables: permiss

Re: [BUGS] Bugs with rules on views/tables: permission denied

2003-02-24 Thread Tom Lane
"Donald Fraser" <[EMAIL PROTECTED]> writes: > As USER chkrule do: > Bugs=3D> INSERT INTO vu_tbl_test (id, s_text) VALUES('1','sometext'); > ERROR: vu_tbl_test: permission denied What I get is ERROR: test_func: permission denied and the needed fix is to grant execute privilege on the fun

Re: [BUGS] Bugs with rules on views/tables: permission denied

2003-02-24 Thread Donald Fraser
- Original Message - From: "Tom Lane" <[EMAIL PROTECTED]>To: "Donald Fraser" <[EMAIL PROTECTED]>Cc: "[ADMIN]" <[EMAIL PROTECTED]>Sent: Monday, February 24, 2003 2:42 PMSubject: Re: [ADMIN] Bugs with rules on views/tables: permission denied > "Donald Fraser" <[EMAIL PROTECTED]> write

Re: [BUGS] bugs

2002-02-19 Thread Tom Lane
Srinivasa R Chava <[EMAIL PROTECTED]> writes: > I'm using postgresql 7.2 > There is a bug in pg_restore. It is not restoring the sequences > properly. and it is failing with views created by pgadmin tool. This is not a bug in pg_restore, but in pg_dump: it's emitting the stuff in the wrong order.

Re: [BUGS] Bugs on COPY command

2001-03-20 Thread Tatsuo Ishii
> I currently using postgresql V7.0.3. > I created a database with UNICODE encoding to store chinese and japanese information. > I have some chinese information created with MS access(excel) and export it to text >file > with delimiter semi-colon ";" . > When I imiport the text file into the tabl

Re: [BUGS] Bugs in to_char function

2000-10-18 Thread Karel Zak
On Tue, 17 Oct 2000, Tom Lane wrote: > "Tom Rogers" <[EMAIL PROTECTED]> writes: > > [to_char] gives the correct meridian value for all AM times but incorrectly > > returns an AM meridian for PM times between 12:00 PM and 1:50:59 PM. > > I believe this is a known bug in the 7.0 implementation of

Re: [BUGS] Bugs in to_char function

2000-10-18 Thread Karel Zak
On Tue, 17 Oct 2000, Tom Rogers wrote: > I wanted to include the following in a select statement: > > to_char(departtime, 'HH12:MI PM') as xdepart Very old story and already fixed in the current CVS. Wait for great 7.1 :-) Karel PS. has this list so

Re: [BUGS] Bugs in to_char function

2000-10-17 Thread Tom Lane
"Tom Rogers" <[EMAIL PROTECTED]> writes: > [to_char] gives the correct meridian value for all AM times but incorrectly > returns an AM meridian for PM times between 12:00 PM and 1:50:59 PM. I believe this is a known bug in the 7.0 implementation of to_char, and is long since fixed in development

Re: [BUGS] bugs

2000-09-06 Thread Stephan Szabo
Yes, right now references constraints require update permissions on the table being referenced in order to grab row level locks on it with SELECT FOR UPDATE. Stephan Szabo [EMAIL PROTECTED] On Thu, 31 Aug 2000, Alexei E. Korneyev wrote: > ==