>> Sorry, I'm not real familiar with pgpool, but have you thought about
>> using an advisory lock on the target table, instead of a "real" lock
>> (SELECT ... FOR UPDATE / LOCK table)? An advisory lock should not
>> interfere with autovacuum. Obviously, this would only work if all the
>> INSERTs in
On tis, 2011-05-31 at 11:49 +0300, Peter Eisentraut wrote:
> 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 usi
On Wed, Jun 1, 2011 at 12:30 PM, Tom Lane wrote:
>> To address this corner
>> case, we should check whether postmaster is really running by sending
>> the signal 0 after we read postmater.pid file? Attached patch does that.
>
> I find myself unimpressed by this approach, because it supposes that t
Robert Haas writes:
> With respect to the root of the issue (why does the anti-join take so
> long?), my first thought was that perhaps the OP was very unlucky and
> had a lot of values that hashed to the same bucket. But that doesn't
> appear to be the case.
Well, yes it is. Notice what the su
Tatsuo Ishii writes:
>> Sorry, I'm not real familiar with pgpool, but have you thought about
>> using an advisory lock on the target table, instead of a "real" lock
>> (SELECT ... FOR UPDATE / LOCK table)?
> Problem with the advisory lock is, it will not work if the target
> table is empty.
(a)
Fujii Masao writes:
> On Sat, May 28, 2011 at 3:13 AM, Tom Lane wrote:
>> Also, if the postmaster.pid file is not there at any point after we've
>> waited 5 seconds, assume the postmaster has failed and report that, rather
>> than almost-certainly-fruitlessly continuing to wait. The pidfile shou
On Sat, May 28, 2011 at 3:13 AM, Tom Lane wrote:
> Also, if the postmaster.pid file is not there at any point after we've
> waited 5 seconds, assume the postmaster has failed and report that, rather
> than almost-certainly-fruitlessly continuing to wait. The pidfile should
> appear almost instant
On Tue, May 31, 2011 at 9:11 PM, Cédric Villemain
wrote:
> Oh damned, I am currently with an eeepc, I'll need 2 days to bench that :-D
> I'll see tomorow.
LOL.
With respect to the root of the issue (why does the anti-join take so
long?), my first thought was that perhaps the OP was very unlucky
Excerpts from David Fetter's message of mar may 31 21:42:08 -0400 2011:
> A colleague brought up an interesting idea that I think is worth
> exploring for all NOT VALID constraints, to wit, is there some way
> (via SQL) to find which rows violate which constraints? I'm picturing
> some kind of fu
Craig Ringer writes:
> On 1/06/2011 9:01 AM, Craig Ringer wrote:
>> Is anyone aware of any changes between 9.0 and 9.1beta that messed with
>> time zone handling and loading?
> By the way, it looks like using any of:
>SELECT 'now'::timestamp;
>SELECT 'now'::timestamptz;
>SELECT curre
> On Tue, May 31, 2011 at 8:08 PM, Tatsuo Ishii wrote:
> [snip]
>> In summary,
>>
>> 1) "LOCK table foo" cannot be used because of conflict with autovacuum
>> 2) "LOCK sequence" just doesn't work
>> 3) "SELECT 1 FROM LOCK sequece" fails after XID wraparound
>>
>> If you have other idea to serializ
On Tue, May 31, 2011 at 8:08 PM, Tatsuo Ishii wrote:
[snip]
> In summary,
>
> 1) "LOCK table foo" cannot be used because of conflict with autovacuum
> 2) "LOCK sequence" just doesn't work
> 3) "SELECT 1 FROM LOCK sequece" fails after XID wraparound
>
> If you have other idea to serialize concurren
On Tue, May 31, 2011 at 12:04:07PM -0400, 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 enfo
Excerpts from Thom Brown's message of mar may 31 20:18:18 -0400 2011:
> On 31 May 2011 18:43, Alvaro Herrera wrote:
> >
> > Here it is -- as a context patch this time, as well.
> There is this scenario:
>
> test=# CREATE DOMAIN things AS INT CHECK (VALUE > 5);
> CREATE DOMAIN
> test=# CREATE TAB
Hi
Unfortunately, I found another way to produce invalid XML values.
template1=# SELECT (XPATH('/*', XMLELEMENT(NAME "root", XMLATTRIBUTES('<' as
xmlns[1];
xpath
---
Since a literal "<" is not allowed in XML attributes, this XML value is not
well-formed. And
On 1/06/2011 9:01 AM, Craig Ringer wrote:
Is anyone aware of any changes between 9.0 and 9.1beta that messed with
time zone handling and loading?
By the way, it looks like using any of:
SELECT 'now'::timestamp;
SELECT 'now'::timestamptz;
SELECT current_time;
SELECT current_date;
SEL
2011/6/1 Robert Haas :
> On Tue, May 31, 2011 at 8:43 PM, Cédric Villemain
> wrote:
>> Yes, while here I noticed that the query was long to be killed.
>> I added a CHECK_FOR_INTERRUPT() in the for(;;) loop in nodeHashjoin.c.
>> It fixes the delay when trying to kill but I don't know about
>> perfo
On 1 June 2011 06:36, Peter Eisentraut wrote:
> It looks like the original DocBook distribution has a limit of 44, but
> someone patched it to 256 on your installation.
>
> But it seems like no one else has seen this problem yet, so it's quite
> suspicious, since surely people have built the docum
On 1/06/2011 1:28 AM, Rikard Pavelic wrote:
The following bug has been logged online:
Bug reference: 6046
Logged by: Rikard Pavelic
Email address: rikard.pave...@zg.htnet.hr
PostgreSQL version: 9.1 beta 1
Operating system: Windows 7 64bit
Description:select current_
On Tue, May 31, 2011 at 7:03 PM, Greg Stark wrote:
> On Tue, May 31, 2011 at 1:07 PM, Alvaro Herrera
> wrote:
>> 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
On Tue, May 31, 2011 at 8:43 PM, Cédric Villemain
wrote:
> Yes, while here I noticed that the query was long to be killed.
> I added a CHECK_FOR_INTERRUPT() in the for(;;) loop in nodeHashjoin.c.
> It fixes the delay when trying to kill but I don't know about
> performance impact this can have in
On 01/06/11 12:32, Mark Kirkwood wrote:
On 01/06/11 12:27, Mark Kirkwood wrote:
Re the code comments - I agree with most of them. However with
respect to the Guc units, I copied the setup for work_mem as that
seemed the most related.
Also - forget to mention - I *thought* you could specify
2011/5/31 Robert Haas :
> On Thu, May 26, 2011 at 8:33 AM, panam wrote:
>> Any third party confirmation?
>
> Yeah, it definitely looks like there is some kind of bug here. Or if
> not a bug, then a very surprising feature. EXPLAIN ANALYZE outputs
> from your proposed test attached. Here's a uni
On 01/06/11 12:27, Mark Kirkwood wrote:
Re the code comments - I agree with most of them. However with respect
to the Guc units, I copied the setup for work_mem as that seemed the
most related.
Also - forget to mention - I *thought* you could specify the temp files
size GUC as KB, MB, GB or
On 01/06/11 09:24, Cédric Villemain wrote:
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 whitespa
On 31 May 2011 18:43, Alvaro Herrera wrote:
>
> 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
There is this scenario:
test=# CREATE DOMAIN things
Hi,
Pgpool currently acquires row locks on sequences to sync sequences
among PostgreSQL servers in "replication mode".
Suppose you have a table t1(i int, j SERIAL) and two sessions are
trying to INSERT the table(initial value of t1_j_seq is 100 on
PostgreSQL server D1 and D2):
S1: INSERT INTO t1
On Tue, May 31, 2011 at 4:11 PM, Tom Lane wrote:
>> Do gistchoose et al expect the triangle function to obey the triangle
>> inequality?
>
> Don't think so.
>
I guess it was obvious but that was "expect the *penalty* function to
obey the triangle inequality"
--
greg
--
Sent via pgsql-hackers
Greg Stark writes:
> On Tue, May 31, 2011 at 2:54 PM, Tom Lane wrote:
>> Prevent problems by clamping negative penalty values to
>> zero. (Just to be really sure, I also made it force NaNs to zero.)
> Do gistchoose et al expect the triangle function to obey the triangle
> inequality?
Don't th
On Tue, May 31, 2011 at 2:54 PM, Tom Lane wrote:
> Prevent problems by clamping negative penalty values to
> zero. (Just to be really sure, I also made it force NaNs to zero.)
Do gistchoose et al expect the triangle function to obey the triangle
inequality? If so isn't it possible treating NaNs
On Tue, May 31, 2011 at 1:07 PM, Alvaro Herrera
wrote:
> 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 allow
On Wed, Jun 1, 2011 at 1:03 AM, Tom Lane wrote:
> 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
Alexander Korotkov writes:
> 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.
Applied, thanks. I threw in an isnan() test too, just to be really sure
funny p
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
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
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'
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
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
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
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 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
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
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
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
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 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.
>
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
>
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
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
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
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
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
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
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
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: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 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 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
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 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
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
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 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
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...
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
> 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 =
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
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 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
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
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 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
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
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.
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
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 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
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
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
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
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
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
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: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
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 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
--
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 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
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
> 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 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
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 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
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
"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
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
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
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 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
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:
>>
1 - 100 of 133 matches
Mail list logo
