Hi folks,
I was working on a little docs patch today, and when I tried to
`make`, openjade choked on an identifier in information_schema.sgml,
which is very much unrelated to my changes:
openjade:information_schema.sgml:828:60:Q: length of name token must
not exceed NAMELEN (44)
Here is a trivia
On 05/31/2011 05:42 AM, Tom Lane wrote:
> Kim Bisgaard writes:
>> On 2011-05-30 04:26, Greg Stark wrote:
>>> My biggest gripe about bugzilla was that it sent you an email with updates
>>> to the bug but you couldn't respond to that email.
>
>> Just checked bugzilla's list of features and they *n
> I don't much like that approach. The standby would need to be able to
> write the backup history file to the archive at the end of backup, and
> we'd have to reintroduce the code to fetch it from archive and, when
> streaming, from the master. At the moment, the archiver doesn't even run
> in the
Kim Bisgaard writes:
> On 2011-05-30 04:26, Greg Stark wrote:
>> My biggest gripe about bugzilla was that it sent you an email with updates
>> to the bug but you couldn't respond to that email.
> Just checked bugzilla's list of features and they *now* lists that as
> supported:
>> File/Modify
Tomasz Chmielewski writes:
> bookstor=# SELECT 1 FROM core_wot_seq FOR UPDATE;
Um ... why are you doing that on a sequence?
> ERROR: could not access status of transaction 1573786613
> DETAIL: Could not open file "pg_clog/05DC": No such file or directory.
This doesn't surprise me too much, beca
On Mon, May 30, 2011 at 6:52 PM, Robert Haas wrote:
> The number of people reading and replying to
> emails on pgsql-bugs is already insufficient, perhaps because of the
> (incorrect) perception that Tom does or will fix everything and no one
> else needs to care. So anything that makes it harde
On 2011-05-30 04:26, Greg Stark wrote:
My biggest gripe about bugzilla was that it sent you an email with updates to
the bug but you couldn't respond to that email.
Just checked bugzilla's list of features and they *now* lists that as supported:
File/Modify Bugs By Email
In addition to the
On 05/30/2011 09:52 PM, Robert Haas wrote:
I have used RT and I found that the
web interface was both difficult to use and unwieldly for tickets
containing large numbers of messages. Maybe those those things have
been improved, but frankly if RT or Bugzilla is the best we can come
up with then
I wrote:
> I've applied patches to fix Martin Pitt's report of peer auth failing on
> FreeBSD-amd64 kernels. I tested it with FreeBSD but do not have the
> resources to check every other platform that uses the same code branch
> in auth_peer. The buildfarm will soon tell us if the patches fail to
On Mon, May 30, 2011 at 09:52:38PM -0400, Robert Haas wrote:
> On Mon, May 30, 2011 at 8:16 PM, Christopher Browne
> wrote:
> > On 2011-05-30 4:31 PM, "Peter Eisentraut" wrote:
> >> On sön, 2011-05-29 at 18:36 -0400, Joe Abbate wrote:
> >> > I've summarizes the main points made in the recent dis
Christopher Browne writes:
> On 2011-05-30 4:31 PM, "Peter Eisentraut" wrote:
>> Based on that, and past discussions, and things we've tried in the past,
>> and gut feeling, and so on, it looks like Request Tracker would appear
>> to be the next best thing to consider trying out. What do people
On 31 May 2011 11:52, Robert Haas wrote:
> I have used RT and I found that the
> web interface was both difficult to use and unwieldly for tickets
> containing large numbers of messages.
A big loud "ditto" from me on this point.
Cheers,
BJ
--
Sent via pgsql-hackers mailing list (pgsql-hackers@
On Sun, May 29, 2011 at 4:29 AM, Noah Misch wrote:
> I don't think it is *necessary*. If we're replaying WAL on a master, we'll
> also
> be resetting unlogged relations after recovery; what we write or do not write
> to
> them in the mean time has no functional impact. Seemed like a sensible
>
On Mon, May 30, 2011 at 8:16 PM, Christopher Browne wrote:
> On 2011-05-30 4:31 PM, "Peter Eisentraut" wrote:
>> On sön, 2011-05-29 at 18:36 -0400, Joe Abbate wrote:
>> > I've summarizes the main points made in the recent discussion and did
>> > some minor additional research on the lists suggest
On 2011-05-30 4:31 PM, "Peter Eisentraut" wrote:
>
> On sön, 2011-05-29 at 18:36 -0400, Joe Abbate wrote:
> > I've summarizes the main points made in the recent discussion and did
> > some minor additional research on the lists suggested by Peter and
> > Chris Browne. Anyone interested in the tra
I've applied patches to fix Martin Pitt's report of peer auth failing on
FreeBSD-amd64 kernels. I tested it with FreeBSD but do not have the
resources to check every other platform that uses the same code branch
in auth_peer. The buildfarm will soon tell us if the patches fail to
compile anywhere
Hi Magnus,
On 05/30/2011 08:45 AM, Magnus Hagander wrote:
> It's fine that a bug tracker *tracks* bugs. It should not control
> them. That's not how this community currently works, and a lot of
> people have said that's how they want it to stay (at least for now).
If I may belabor the point, what
On 26.05.2011 00:31, Tom Lane wrote:
The main annoyance here is that standalone expressions may now need
Param slots to execute, which will complicate places that need to
evaluate them, but there's probably no way around that
Yeah, I can see two complications:
1. Domain constraints
Domain con
> Why is it necessary to replay the operation only on the slave? Can we
> just use XLOG_HEAP_NEWPAGE?
Uh, I don't know why but I thought I shouldn't log a page on the master,
since all the pages are already there and fsync-ed. But if it makes no harm,
I can easily use XLOG_HEAP_NEWPAGE (of co
Hi!
During my work on GSoC project, I found bad perfomace of GiST for point
datatype. It appears even on uniform random data.
test=# create table test as (select point(random(), random()) from
generate_series(1, 100));
SELECT 100
test=# create index test_idx on test using gist(point);
CRE
Hi Greg,
On 05/29/2011 10:26 PM, Greg Stark wrote:
> On Sun, May 29, 2011 at 3:36 PM, Joe Abbate wrote:
>> Anyone interested in the tracker, please visit
>> http://wiki.postgresql.org/wiki/TrackerDiscussion and add your
>> feedback/input.
>
> I think this illustrates exactly what we *don't* wan
Hi,
Cube code provided by postgres contrib folder. It uses the NDBOX structure.
On creating index, it's size increase at a high rate.
On inserting some tuple and creating indexes its behaviour is shown below.
1. When there is only one tuple
select pg_size_pretty(pg_relation_size('cubtest'));
On Sun, May 29, 2011 at 10:09 PM, Stefan Kaltenbrunner
wrote:
> well bugzilla has an inbound email interface as well that can both be
> used to creande and to manipulate bugs (as in "mails that have the
> bug-id in the subject will be added as a comment").
Ugh, putting it in the subject plays poo
Hello
I would like to know what is the process to get new applications accepted for
inclusion in the stack builder (namely the eZ Publish cms).
I would be ready spend some time to package the application according to some specific format, and to host the built package on some dedicated server i
On 30.05.2011 17:10, Kevin Grittner wrote:
Heikki Linnakangas wrote:
On 26.05.2011 06:19, Kevin Grittner wrote:
I did some of that in the comments, and I think I understand it
now. See attached patch. Does that look right to you?
! * A serialization failure can only occur if there is a danger
On Mon, May 30, 2011 at 20:39, Tom Lane wrote:
> Magnus Hagander writes:
>> On Fri, May 13, 2011 at 00:21, Tom Lane wrote:
>>> Magnus Hagander writes:
On Tue, May 10, 2011 at 05:39, Tom Lane wrote:
> I wouldn't have a problem with making the Windows port throw an error
> for "loca
On Mon, May 30, 2011 at 2:26 AM, Greg Stark wrote:
> On Sun, May 29, 2011 at 3:36 PM, Joe Abbate wrote:
>> Anyone interested in the tracker, please visit
>> http://wiki.postgresql.org/wiki/TrackerDiscussion and add your
>> feedback/input.
>
> I think this illustrates exactly what we *don't* want
Hi,
Cube code provided by postgres contrib folder. It uses the NDBOX structure.
On creating index, it's size increase at a high rate.
On inserting some tuple and creating indexes its behaviour is shown below.
1. When there is only one tuple
select pg_size_pretty(pg_relation_
size('cubtest'))
On 26.05.2011 06:19, Kevin Grittner wrote:
/*
* Check whether the writer has become a pivot with an out-conflict
* committed transaction, while neither reader nor writer is committed.
If
* the reader is a READ ONLY transaction, there is only a serialization
On Mon, May 30, 2011 at 16:52, Joe Abbate wrote:
> Hi Magnus,
>
> On 05/30/2011 08:45 AM, Magnus Hagander wrote:
>> It's fine that a bug tracker *tracks* bugs. It should not control
>> them. That's not how this community currently works, and a lot of
>> people have said that's how they want it to
On 05/27/2011 08:36 AM, MauMau wrote:
> I posted a patch for bug #6011 to pgsql-hackers several days ago. How
> can I check the status of bug fixes? I'm worried that the patch might
> be forgotten, because bug #5842 was missed for two months until Bruce
> noticed it.
Discussion here seems to have
Hi
The in-core XPATH() function currently only handles XPath expressions which
return a node set correctly. For XPath expressions which return boolean,
numeric or string values, XPATH() returns an empty array. (This is the case
for XPath expressions whose top-level syntactic construct isn't a path
On Monday, May 30, 2011 07:30:37 AM Greg Smith wrote:
> Trac
While I am not a fan of trac there is a plugin for that that works reasonable
well and isn't that hard to customize if needed:
https://subtrac.sara.nl/oss/email2trac
Andres
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgre
On sön, 2011-05-29 at 11:05 -0400, Tom Lane wrote:
> If it has only a partial view of the set of bugs being worked on, it's
> not going to meet the goals that are being claimed for it.
>
> I don't doubt that somebody could run around and link every discussion
> about a bug into the tracker. I'm j
On Mon, May 30, 2011 at 04:26, Greg Stark wrote:
> On Sun, May 29, 2011 at 3:36 PM, Joe Abbate wrote:
>> Anyone interested in the tracker, please visit
>> http://wiki.postgresql.org/wiki/TrackerDiscussion and add your
>> feedback/input.
>
> I think this illustrates exactly what we *don't* want t
On sön, 2011-05-29 at 18:36 -0400, Joe Abbate wrote:
> I've summarizes the main points made in the recent discussion and did
> some minor additional research on the lists suggested by Peter and
> Chris Browne. Anyone interested in the tracker, please visit
> http://wiki.postgresql.org/wiki/Tracker
On 05/29/2011 05:17 AM, Peter Eisentraut wrote:
Here is a list to choose from:
http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems
I turned this into a spreadsheet to sort and prune more easily; if
anyone wants that let me know, it's not terribly useful beyond what I'm
posti
Excerpts from Greg Stark's message of dom may 29 22:26:21 -0400 2011:
> My ideal bug tracker is the debian one which basically stays out of
> your way and lets you cc any message to a specific bug at
> n...@bugs.debian.org which archives that message in the bug and sends
> it to anyone listening t
Magnus Hagander writes:
> On Fri, May 13, 2011 at 00:21, Tom Lane wrote:
>> Magnus Hagander writes:
>>> On Tue, May 10, 2011 at 05:39, Tom Lane wrote:
I wouldn't have a problem with making the Windows port throw an error
for "local" lines. We'd have to fix initdb to remove that line f
[The first attempt to send this shows as undeliverable to the list.
Resending for completeness and coherency of archives. Apologies to
those getting duplicates.]
> Heikki Linnakangas wrote:
> On 26.05.2011 06:19, Kevin Grittner wrote:
>
>> /*
>> * Check whether the writer has become a pivot wit
On Fri, May 13, 2011 at 00:21, Tom Lane wrote:
> Magnus Hagander writes:
>> On Tue, May 10, 2011 at 05:39, Tom Lane wrote:
>>> I wouldn't have a problem with making the Windows port throw an error
>>> for "local" lines. We'd have to fix initdb to remove that line from the
>>> sample file (if it
Heikki Linnakangas writes:
> I think we can work around both of those by just saving and restoring
> the value of each Param that we set while evaluating an expression,
Huh? That's a waste of time and effort. Just make sure that each such
spot has its own Param number. That's why I'm telling
On 24.05.2011 15:22, Alexander Korotkov wrote:
During preparing patch of my GSoC project I found reasonable to
move childoffnum (GISTInsertStack structure) from parent to child. This
means that now child have childoffnum of parent's link to child. It allows
to maintain entire parts of tree in tha
On 05/30/2011 04:26 AM, Greg Stark wrote:
> On Sun, May 29, 2011 at 3:36 PM, Joe Abbate wrote:
>> Anyone interested in the tracker, please visit
>> http://wiki.postgresql.org/wiki/TrackerDiscussion and add your
>> feedback/input.
>
> I think this illustrates exactly what we *don't* want to happe
On 05/30/2011 10:57 AM, Magnus Hagander wrote:
> The case I want to avoid is (a). And if it's possible to make (b) just
> be the -hackers mailinglist and putting a keyword in the right place,
Did you mean the -bugs mailing list?
On the subject of keywords, considering Robert's suggestion to
"Asso
45 matches
Mail list logo
