On 31.05.2011 07:46, Jun Ishiduka wrote:
>> 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 m
On 30.05.2011 21:51, Nick Raj wrote:
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_s
> I think
> we need a detailed design document for how this is all going to work.
> We need to not only handle the master properly but also handle the
> slave properly. Consider, for example, the case where the slave
> begins to replay the transaction, reaches a restartpoint after
> replaying
On Mon, May 30, 2011 at 9:45 AM, Gaetano Giunta
wrote:
> 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 specifi
On mån, 2011-05-30 at 22:43 -0400, Andrew Dunstan wrote:
> One of the conclusions the study group came to was that there should
> be good integration between the tracker system and the SCM. That was
> in the days before distributed SCMs were common, and in a commercial
> context, so I'm not sure ho
On mån, 2011-05-30 at 21:52 -0400, 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 31.05.2011 01:07, Alexander Korotkov wrote:
In gist_box_penalty function floating point error in line
*result = (float) (size_box(ud) - size_box(origentry->key));
sometimes makes *result a very small negative number.
I beleive that best place to fix it is gistpenalty function. The attached
On mån, 2011-05-30 at 20:16 -0400, Christopher Browne wrote:
> My suspicion is that RT may be rather a lot heavier weight in terms of
> how it would have to affect process than people would be happy with.
>
>
> What has been pretty clearly expressed is that various of the
> developers prefer for
On mån, 2011-05-30 at 21:52 -0400, 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 co
On 31.05.2011 05:16, Tom Lane wrote:
> 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 dir
On Mon, May 30, 2011 at 07:42, Greg Stark wrote:
> 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
On Tue, May 31, 2011 at 07:08, Stefan Kaltenbrunner
wrote:
> 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
On mån, 2011-05-30 at 22:17 -0400, Tom Lane wrote:
> 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
2011/5/31 Heikki Linnakangas :
> On 31.05.2011 07:46, Jun Ishiduka wrote:
>>> 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
>>>
On mån, 2011-05-30 at 01:30 -0400, Greg Smith wrote:
> Greg Stark is right that Debbugs has a lot of interesting features
> similar to the desired workflow here. It's not tied to just Debian
> anymore; the GNU project is also using it now.
For the benefit of others, I suppose you are referring
2011/5/30, Nick Raj :
> 3. When tuples are 5 lakh
For the benefit of the others: "5 lakh" seems to mean 500,000.
http://en.wikipedia.org/wiki/Lakh>
Nicolas
--
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
Sent via pgsql-hackers mailing list (pgsql-ha
On tis, 2011-05-31 at 10:36 +0200, Magnus Hagander wrote:
> I get the feeling we're approaching this backwards. Wouldn't the
> normal way to do it be to define the workflow we *want*, and then
> figure out which bugtracker works for that or requires the least
> changes for that, rather than to try
On Tue, May 31, 2011 at 12:06 PM, Heikki Linnakangas <
heikki.linnakan...@enterprisedb.com> wrote:
> The documentation should be fixed too.
>
Patch with documentation fix is attached.
I tried to reproduce this problem on another computer with Windows, but
problem doesn't occurs. So, seems that it
On Tue, May 31, 2011 at 11:47, Peter Eisentraut wrote:
> On tis, 2011-05-31 at 10:36 +0200, Magnus Hagander wrote:
>> I get the feeling we're approaching this backwards. Wouldn't the
>> normal way to do it be to define the workflow we *want*, and then
>> figure out which bugtracker works for that
From: "Robert Haas"
It might be useful, in this situation, for the OP to add this patch to
the CommitFest application.
https://commitfest.postgresql.org/action/commitfest_view/open
"Greg Smith" wrote in message
news:4de1a8e7.1030...@2ndquadrant.com...
Discussion here seems to have wandered
On 05/31/2011 06:41 AM, Magnus Hagander wrote:
We already have a search system that works reasonably well for the archives...
I trust this weas a piece of sarcasm. I spoke to more than a few people
at pgcon and nobody had a good word to say about the search system on
the archives.
cheers
On Tue, May 31, 2011 at 14:44, Andrew Dunstan wrote:
>
>
> On 05/31/2011 06:41 AM, Magnus Hagander wrote:
>>
>> We already have a search system that works reasonably well for the
>> archives...
>>
>
> I trust this weas a piece of sarcasm. I spoke to more than a few people at
> pgcon and nobody had
On 05/31/2011 04:01 AM, Peter Eisentraut wrote:
On mån, 2011-05-30 at 22:43 -0400, Andrew Dunstan wrote:
One of the conclusions the study group came to was that there should
be good integration between the tracker system and the SCM. That was
in the days before distributed SCMs were common, an
On tis, 2011-05-31 at 08:44 -0400, Andrew Dunstan wrote:
>
> On 05/31/2011 06:41 AM, Magnus Hagander wrote:
> > We already have a search system that works reasonably well for the
> > archives...
> >
>
> I trust this weas a piece of sarcasm. I spoke to more than a few people
> at pgcon and nobod
On Wed, May 25, 2011 at 3:35 PM, Tom Lane wrote:
> Simon Riggs writes:
>> On Wed, May 25, 2011 at 1:44 PM, Robert Haas wrote:
>>> On Wed, May 25, 2011 at 8:27 AM, Simon Riggs wrote:
Design seemed relatively easy from there: put local lock table in
shared memory for all procs. We then
On Tue, May 31, 2011 at 15:07, Andrew Dunstan wrote:
>
>
> On 05/31/2011 04:01 AM, Peter Eisentraut wrote:
>>
>> On mån, 2011-05-30 at 22:43 -0400, Andrew Dunstan wrote:
>>>
>>> One of the conclusions the study group came to was that there should
>>> be good integration between the tracker system
On Tue, May 31, 2011 at 4:12 AM, Peter Eisentraut wrote:
> On mån, 2011-05-30 at 21:52 -0400, 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
>> be
Tomasz Chmielewski writes:
> On 31.05.2011 05:16, Tom Lane wrote:
>> I think the most appropriate solution may be to disallow SELECT FOR
>> UPDATE/SHARE on sequences ... so if you have a good reason why we
>> shouldn't do so, please explain it.
> I grepped the sources of the application using pos
On Tue, May 31, 2011 at 4:36 AM, Magnus Hagander wrote:
> I get the feeling we're approaching this backwards. Wouldn't the
> normal way to do it be to define the workflow we *want*, and then
> figure out which bugtracker works for that or requires the least
> changes for that, rather than to try t
On Tue, May 31, 2011 at 02:58:02PM +0200, Magnus Hagander wrote:
> On Tue, May 31, 2011 at 14:44, Andrew Dunstan wrote:
> >
> >
> > On 05/31/2011 06:41 AM, Magnus Hagander wrote:
> >>
> >> We already have a search system that works reasonably well for the
> >> archives...
> >>
> >
> > I trust this
On Tue, May 31, 2011 at 9:22 AM, Simon Riggs wrote:
> The basis for this is that weak locks do not conflict with each other,
> whereas strong locks conflict with both strong and weak locks.
> (There's a couple of special cases which I ignore for now).
> (Using Robert's description of strong/weak l
On 05/30/2011 07:57 PM, Tom Lane 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 tel
On 05/31/2011 09:33 AM, Robert Haas wrote:
IIRC, both of them think that you should log into the web interface to
send emails (which, in the case of Bugzilla, don't permit replies),
rather than sending emails that show up in the web interface.
I think you probably need to look at Bugzilla aga
Robert Haas writes:
> On Tue, May 31, 2011 at 4:36 AM, Magnus Hagander wrote:
>> So in order to start a brand new bikeshed to paint on, have we even
>> considered a very trivial workflow like letting the bugtracker
>> actually *only* track our existing lists and archives. That would
>> mean:
>>
On Tue, May 31, 2011 at 09:33:33AM -0400, Robert Haas wrote:
> On Tue, May 31, 2011 at 4:12 AM, Peter Eisentraut wrote:
> > On mån, 2011-05-30 at 21:52 -0400, Robert Haas wrote:
> >> I have used RT and I found that the
> >> web interface was both difficult to use and unwieldly for tickets
> >> con
Andrew Dunstan writes:
> On 05/31/2011 06:41 AM, Magnus Hagander wrote:
>> We already have a search system that works reasonably well for the
>> archives...
> I trust this weas a piece of sarcasm. I spoke to more than a few people
> at pgcon and nobody had a good word to say about the search sy
On May 26, 2011, at 12:41 PM, Alvaro Herrera wrote:
> Yes, I think the lock-up is better than weird behavior. Maybe we should
> add a short note in a postgresql.conf comment to this effect, so that it
> doesn't surprise anyone that deletes or comments out the line.
+1 on both counts.
--
Jim C. Na
On Tue, May 31, 2011 at 16:21, Kevin Grittner
wrote:
> "k...@rice.edu" wrote:
>
>> maybe we can do some tweaking our search engine to improve it.
>
> A custom dictionary to carefully add a few synonyms might go a long
> way. I often need to try a number of permutations of likely words
> to get r
"k...@rice.edu" wrote:
> maybe we can do some tweaking our search engine to improve it.
A custom dictionary to carefully add a few synonyms might go a long
way. I often need to try a number of permutations of likely words
to get relevant hits.
Including the subject line in searches, with a
Sorry for the self-reply but I figured it'd be helpful to add information
that I discovered only after my initial post.
On May30, 2011, at 15:17 , Florian Pflug wrote:
> The XPath expression 'name(/*)', for example, is supposed to return 'root'
> when applied to the XML fragment ''. Postgres,
> ho
On Tue, May 31, 2011 at 09:36:00AM -0400, Tom Lane wrote:
> Andrew Dunstan writes:
> > On 05/31/2011 06:41 AM, Magnus Hagander wrote:
> >> We already have a search system that works reasonably well for the
> >> archives...
>
> > I trust this weas a piece of sarcasm. I spoke to more than a few pe
Magnus Hagander wrote:
> Any patches are definitely welcome - you can find the search
> system at
> https://pgweb.postgresql.org/browser/trunk/portal/tools/search
> :-)
>
> (for the archives, you're probably most interested in
> classes/ArchiveIndexer.class.php and the sql/functions.sql file)
On 05/31/2011 04:36 AM, Magnus Hagander wrote:
> So in order to start a brand new bikeshed to paint on, have we even
> considered a very trivial workflow like letting the bugtracker
> actually *only* track our existing lists and archives. That would
> mean:
>
> * Mailing lists are *primary*, and t
> Tomasz Chmielewski writes:
>> On 31.05.2011 05:16, Tom Lane wrote:
>>> I think the most appropriate solution may be to disallow SELECT FOR
>>> UPDATE/SHARE on sequences ... so if you have a good reason why we
>>> shouldn't do so, please explain it.
>
>> I grepped the sources of the application
On Tue, May 31, 2011 at 10:02 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Tue, May 31, 2011 at 4:36 AM, Magnus Hagander wrote:
>>> So in order to start a brand new bikeshed to paint on, have we even
>>> considered a very trivial workflow like letting the bugtracker
>>> actually *only* track
On Tue, May 31, 2011 at 9:59 AM, Andrew Dunstan wrote:
> On 05/31/2011 09:33 AM, Robert Haas wrote:
>>
>> IIRC, both of them think that you should log into the web interface to
>> send emails (which, in the case of Bugzilla, don't permit replies),
>> rather than sending emails that show up in the
Excerpts from Brendan Jurd's message of mar may 31 02:17:22 -0400 2011:
> 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_sch
On Sat, May 28, 2011 at 4:39 AM, nil nil wrote:
> Sir,
> i am developing a patch for postgresql in c language. i want to
> know that how can i integrate my patch with postgresql.
> regards
> emman
This might be a good place to start:
http://wiki.postgresql.org/wiki/Developer_FAQ
--
On Sat, May 28, 2011 at 4:53 AM, nil nil wrote:
>
> sir,
> i am developnig a patch and as per instructionsdescribed on this
> site http://wiki.postgresql.org/wiki/Developer_FAQ it is specifed on the
> link that along with unix platform we have to use GCC, GNU
> Make, GDB, Autoconf but i don
On Tue, May 31, 2011 at 3:39 AM, Leonardo Francalanci wrote:
>> I think
>> we need a detailed design document for how this is all going to work.
>> We need to not only handle the master properly but also handle the
>> slave properly. Consider, for example, the case where the slave
>> begins to
Excerpts from Joe Abbate's message of mar may 31 10:43:07 -0400 2011:
> I have a web crawler for a website I maintain that I could modify to
> crawl through the archives of -bugs, say from 5 Dec 2003 where the first
> bug with the new format appears, and capture the structured data
> (reference, l
On Tue, May 31, 2011 at 3:22 PM, Alvaro Herrera
wrote:
> Excerpts from Brendan Jurd's message of mar may 31 02:17:22 -0400 2011:
>> 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 ve
Robert Haas writes:
> On Tue, May 31, 2011 at 10:02 AM, Tom Lane wrote:
>> I kinda wonder why the CF app doesn't work like that, actually.
>> (Yeah, I know the poor thread linking in the archives is an issue.)
> I thought this pretty much WAS how the CF app works, except that it's
> for patches
This patch allows you to initially declare a CHECK constraint as NOT
VALID, similar to what we already allow for foreign keys. That is, you
create the constraint without scanning the table and after it is
committed, it is enforced for new rows; later, all rows are checked by
running ALTER TABLE VA
Christopher Browne writes:
> On Tue, May 31, 2011 at 3:22 PM, Alvaro Herrera
> wrote:
>> Excerpts from Brendan Jurd's message of mar may 31 02:17:22 -0400 2011:
>>> openjade:information_schema.sgml:828:60:Q: length of name token must
>>> not exceed NAMELEN (44)
>> Odd. I tried it here and it do
Hola Alvaro,
On 05/31/2011 11:38 AM, Alvaro Herrera wrote:
> I think this would be easier if you crawled the monthly mboxen instead
> of the web archives. It'd be preferable to use message-ids to identify
> messages rather than year-and-month based URLs.
I can capture the message-ids, as well as
On 30.05.2011 17:21, Tom Lane wrote:
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 Pa
On Tue, May 31, 2011 at 12:01 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Tue, May 31, 2011 at 10:02 AM, Tom Lane wrote:
>>> I kinda wonder why the CF app doesn't work like that, actually.
>>> (Yeah, I know the poor thread linking in the archives is an issue.)
>
>> I thought this pretty much
On Tue, May 31, 2011 at 11:04 AM, Alvaro Herrera
wrote:
> This patch allows you to initially declare a CHECK constraint as NOT
> VALID
seems you forgot to add the patch itself
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent v
I wrote:
> BTW, after looking more closely at the buildfarm configure logs, it
> appears that both OpenBSD and NetBSD have getpeereid(), which means
> that they don't use this code at all. It is currently looking to me
> like the HAVE_STRUCT_FCRED and HAVE_STRUCT_SOCKCRED variants are dead
> code.
Joe Abbate wrote:
> I assume a link such as
>
> http://archives.postgresql.org/pgsql-bugs/2003-12/msg00046.php
>
> would be easier to follow than
>
> <20031205173035.ga16...@wolff.to>
The point is that the community seems to have reached a consensus
that they would rather use this URL for t
Excerpts from Kevin Grittner's message of mar may 31 12:41:59 -0400 2011:
> Joe Abbate wrote:
>
> > I assume a link such as
> >
> > http://archives.postgresql.org/pgsql-bugs/2003-12/msg00046.php
> >
> > would be easier to follow than
> >
> > <20031205173035.ga16...@wolff.to>
>
> The point i
Excerpts from Alvaro Herrera's message of mar may 31 12:39:48 -0400 2011:
> Excerpts from Jaime Casanova's message of mar may 31 12:24:09 -0400 2011:
> > On Tue, May 31, 2011 at 11:04 AM, Alvaro Herrera
> > wrote:
> > > This patch allows you to initially declare a CHECK constraint as NOT
> > > VAL
Excerpts from Jaime Casanova's message of mar may 31 12:24:09 -0400 2011:
> On Tue, May 31, 2011 at 11:04 AM, Alvaro Herrera
> wrote:
> > This patch allows you to initially declare a CHECK constraint as NOT
> > VALID
>
> seems you forgot to add the patch itself
oops ... another bug in my email c
On Tue, May 31, 2011 at 04:19:29PM +0200, Florian Pflug wrote:
> Sorry for the self-reply but I figured it'd be helpful to add information
> that I discovered only after my initial post.
>
> On May30, 2011, at 15:17 , Florian Pflug wrote:
> > The XPath expression 'name(/*)', for example, is suppos
On Tue, May 31, 2011 at 12:04 PM, Alvaro Herrera
wrote:
> This patch allows you to initially declare a CHECK constraint as NOT
> VALID, similar to what we already allow for foreign keys. That is, you
> create the constraint without scanning the table and after it is
> committed, it is enforced fo
On 05/31/2011 01:12 AM, Peter Eisentraut wrote:
On mån, 2011-05-30 at 21:52 -0400, 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 fran
> Well, I sort of assumed the design was OK, too, but the more we talk
> about this WAL-logging stuff, the less convinced I am that I really
> understand the problem. :-(
I see. In fact, I think nobody thought about restart points...
To sum up:
1) everything seems ok when in the wal_level =
Alvaro Herrera wrote:
> This patch allows you to initially declare a CHECK constraint as
> NOT VALID, similar to what we already allow for foreign keys.
> That is, you create the constraint without scanning the table and
< after it is committed, it is enforced for new rows; later, all
> rows ar
On Tue, May 31, 2011 at 19:10, Joe Abbate wrote:
> On 05/31/2011 12:41 PM, Kevin Grittner wrote:
>> The point is that the community seems to have reached a consensus
>> that they would rather use this URL for the above message:
>>
>> http://archives.postgresql.org/message-id/20031205173035.ga16...
On tis, 2011-05-31 at 14:58 +0200, Magnus Hagander wrote:
> But sure, it can probably be improved. But what people are then
> basically asying is that tsearch isn't good enough for searching.
For one thing, there should be more structured search possibilities,
such as by date or author or subject
Here it is -- as a context patch this time, as well.
--
Álvaro Herrera
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
0001-Enable-CHECK-constraints-to-be-declared-NOT-VALID.patch
Description: Binary data
--
Sent via pgsql-h
On 05/31/2011 12:41 PM, Kevin Grittner wrote:
> The point is that the community seems to have reached a consensus
> that they would rather use this URL for the above message:
>
> http://archives.postgresql.org/message-id/20031205173035.ga16...@wolff.to
OK, as I said, I can still capture the mess
On Tue, May 31, 2011 at 11:35:01AM -0500, Kevin Grittner wrote:
> Alvaro Herrera wrote:
>
> > This patch allows you to initially declare a CHECK constraint as
> > NOT VALID, similar to what we already allow for foreign keys.
> > That is, you create the constraint without scanning the table and
Excerpts from Joshua D. Drake's message of mar may 31 12:32:43 -0400 2011:
> > Given that you have been one of the people calling for a bug tracker,
> > and these are the two most widely used systems available, what's wrong
> > with them and what else would you suggest?
>
> Just FYI, CMD uses red
On 05/31/2011 01:13 PM, Magnus Hagander wrote:
> Just to be clear, crawling the current archives for this info is
> probably the easiest part of the whole project. In fact, the majority
> of the information you'd need is *already* in a postgresql database on
> search.postgresql.org.
Does that data
On Sun, May 29, 2011 at 4:05 PM, Tom Lane wrote:
> Peter Eisentraut writes:
>> That doesn't mean that better integration cannot be worked on later, but
>> this illusion that a bug tracker must have magical total awareness of
>> the entire flow of information in the project from day one is an
>> i
On Tue, May 31, 2011 at 19:59, Joe Abbate wrote:
> On 05/31/2011 01:13 PM, Magnus Hagander wrote:
>> Just to be clear, crawling the current archives for this info is
>> probably the easiest part of the whole project. In fact, the majority
>> of the information you'd need is *already* in a postgres
On 05/31/2011 11:05 AM, Alvaro Herrera wrote:
Excerpts from Joshua D. Drake's message of mar may 31 12:32:43 -0400 2011:
Given that you have been one of the people calling for a bug tracker,
and these are the two most widely used systems available, what's wrong
with them and what else would you
On Tue, May 31, 2011 at 19:37, Peter Eisentraut wrote:
> On tis, 2011-05-31 at 14:58 +0200, Magnus Hagander wrote:
>> But sure, it can probably be improved. But what people are then
>> basically asying is that tsearch isn't good enough for searching.
>
> For one thing, there should be more structu
Hi
While trying to figure out sensible semantics for XPATH() and scalar-value
returning XPath expressions, I've stumbled upon a bug in XPATH() that allows
invalid XML values to be produced. This is a serious problem because should
such invalid values get inserted into an XML column, an un-resto
2011/5/31 Alvaro Herrera :
> Excerpts from Joshua D. Drake's message of mar may 31 12:32:43 -0400 2011:
>> Alvaro has also brought up the system that Debian uses which is actually
>> email based versus web based.
>
> Yeah, that's debbugs, which has been mentioned elsewhere in this thread.
I like t
On May31, 2011, at 19:15 , Ross J. Reedstrom wrote:
> What you describe, making XPATH return something for the scalar
> functions, is sorely needed. Constraining the return values to be valid
> XML fragments is the sort of wart that makes XML processing in
> postgresql seem odd to those familiar wi
On tis, 2011-05-31 at 11:59 -0400, Tom Lane wrote:
> However, FreeBSD does have, and Debian/kFreeBSD does expose,
> getsockopt(LOCAL_PEERCRED), which turns out to be functionally
> equivalent to SO_PEERCRED: in particular, you can just call it and get
> the answer without having to fool with gettin
Excerpts from Ross J. Reedstrom's message of mar may 31 14:02:04 -0400 2011:
> Follows from one of the practical maxims of databases: "The data is
> always dirty" Being able to have the constraints enforced at least for
> new data allows you to at least fence the bad data, and have a shot at
> fix
Alvaro Herrera writes:
> Excerpts from Kevin Grittner's message of mar may 31 12:41:59 -0400 2011:
>> The point is that the community seems to have reached a consensus
>> that they would rather use this URL for the above message:
>>
>> http://archives.postgresql.org/message-id/20031205173035.ga1
On tis, 2011-05-31 at 12:13 -0400, Tom Lane wrote:
> Christopher Browne writes:
> > On Tue, May 31, 2011 at 3:22 PM, Alvaro Herrera
> > wrote:
> >> Excerpts from Brendan Jurd's message of mar may 31 02:17:22 -0400 2011:
> >>> openjade:information_schema.sgml:828:60:Q: length of name token must
>
On Tue, May 31, 2011 at 12:38 PM, Peter Eisentraut wrote:
>> So what I'm now thinking is we should rip out the control-message
>> implementation altogether, and instead use LOCAL_PEERCRED. This is
>> probably not something to back-patch, but it would make things a lot
>> cleaner going forward.
>
All,
Let me mention some of the reasons we as a project could use a bug
tracker which have nothing to do with actually fixing bugs.
(1) Testing: a bug tracker could be used for beta testing instead of the
ad-hoc system I'm writing. Assuming it has the right features, of course.
(2) User informa
On 05/31/2011 04:36 PM, Peter Eisentraut wrote:
But it seems like no one else has seen this problem yet, so it's quite
suspicious, since surely people have built the documentation in the last
few months.
I have two buildfarm members with stock openjade/docbook installations
building the doc
Greg Stark writes:
> On Tue, May 31, 2011 at 12:38 PM, Peter Eisentraut wrote:
>> Oh yes, no point in having complicated code that doesn't get exercised.
> This does amount to desupporting old versions of those OSes in newer
> versions of Postgres, at least for this one feature. Since you're
> s
Hello
here is a partial review of your patch, better than keeping it
sleeping in the commitfest queue I hope.
Submission review
* The patch is not in context diff format.
* The patch apply, but contains some extra whitespace.
* Documentation is here but not explicit
Excerpts from Dimitri Fontaine's message of mar may 31 16:11:35 -0400 2011:
> Check out the following POC, which needs to get migrated into a django
> application for the upcoming new infrastructure:
>
> http://archives.beccati.org/
>
> It uses AOX (http://aox.org/) and as such is baked by a P
Hello,
Is there any way to retrieve the actual variable names (as were given
during Stored Procedure definition) for the corresponding var_ids in
pl/plpgsql/src/pl_exec.c ?
I have modified some PostgreSQL code for my own project and I track some
information for functions during their execution
Excerpts from Josh Berkus's message of mar may 31 17:05:23 -0400 2011:
> BTW, we talked to Debian about debbugs ages ago, and the Debian project
> said that far too much of debbugs was not portable to other projects.
The good news is that the GNU folk proved them wrong, as evidenced
elsewhere in
2011/5/31 Josh Berkus :
> All,
>
> Let me mention some of the reasons we as a project could use a bug
> tracker which have nothing to do with actually fixing bugs.
>
> (1) Testing: a bug tracker could be used for beta testing instead of the
> ad-hoc system I'm writing. Assuming it has the right fe
On Wed, Jun 1, 2011 at 12:22 AM, Tom Lane wrote:
> Greg Stark writes:
>> On Tue, May 31, 2011 at 12:38 PM, Peter Eisentraut wrote:
>>> Oh yes, no point in having complicated code that doesn't get exercised.
>
>> This does amount to desupporting old versions of those OSes in newer
>> versions of
Marko Kreen writes:
> My suggestion would be to use getpeereid() everywhere.
> And just have compat getpeereid() implementation on non-BSD
> platforms. This would minimize ifdeffery in core core.
Hm, maybe. I'd be for this if we had more than two call sites, but
as things stand I'm not sure it'
2011/5/31, Tom Lane :
> Unless maybe there's a kFreeBSD-like project out there with NetBSD as
> the kernel?)
There used to be an attempt by Debian (called GNU/NetBSD), but that
has since long been abandoned. I don't know of any other similar
projects.
http://www.debian.org/ports/netbsd/>
Wikipe
Dimitris Karampinas writes:
> Is there any way to retrieve the actual variable names (as were given
> during Stored Procedure definition) for the corresponding var_ids in
> pl/plpgsql/src/pl_exec.c ?
As of 9.0, you could dig through the namespace stack looking for a
match to the dno (datum numb
1 - 100 of 133 matches
Mail list logo
