"Kevin Grittner" writes:
> Alvaro Herrera wrote:
>> you'd be required to type something like
>> psql \"nEWuSer\"
> Although we do that with some command-line arguments, like the
> pg_dump -t switch. Not arguing for any particular course here, just
> noting the inconsistency.
Right. -t is lik
Tom Lane wrote:
> Bruce Momjian writes:
> > Community, do we want to make a permission reset cause the column to
> > become null?
>
> That's not a permission reset.
>
> >> I just need to know if the brackets are normal when all the privileges are
> >> remove. Or how to reset the privileges (ACL)
Alvaro Herrera wrote:
> you'd be required to type something like
> psql \"nEWuSer\"
Although we do that with some command-line arguments, like the
pg_dump -t switch. Not arguing for any particular course here, just
noting the inconsistency.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsq
Evan Nelson escribió:
>
> The following bug has been logged online:
>
> Bug reference: 5431
> Logged by: Evan Nelson
> Email address: ean5...@gmail.com
> PostgreSQL version: 8.4
> Operating system: Ubuntu 9.10
> Description:CREATE USER is not case sensitive, but psql
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
The following bug has been logged online:
Bug reference: 5431
Logged by: Evan Nelson
Email address: ean5...@gmail.com
PostgreSQL version: 8.4
Operating system: Ubuntu 9.10
Description:CREATE USER is not case sensitive, but psql command line
arguments are
Details:
Wh
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
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.
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",
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
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
The following bug has been logged online:
Bug reference: 5430
Logged by: Jamie Strachan
Email address: frostfr...@yahoo.com
PostgreSQL version: 8.4.3-2PGDG.el4
Operating system: CentOS 4
Description:initdb fails due to permissions of /usr/share/pgsql
Details:
Hello,
The following bug has been logged online:
Bug reference: 5429
Logged by: goutham
Email address: jgowt...@gmail.com
PostgreSQL version: 8.1.9
Operating system: Windows
Description:Driver issue
Details:
I am using Driver = PostgreSQL UNICODE.
I am retrieving the datas
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
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
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
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"
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
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.
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?
20 matches
Mail list logo
