Hi,
http://archives.postgresql.org/pgsql-hackers/2009-07/msg00191.php
In line with Robert's suggestion, I submit the signal multiplexing patch
as self-contained one.
This patch provides support for multiplexing SIGUSR1 signal.
The upcoming synchronous replication patch needs a signal, but we've
On Friday 03 July 2009 05:16:41 Robert Haas wrote:
> On Thu, Jul 2, 2009 at 3:42 PM, Zdenek Kotala wrote:
> > Josh Berkus píše v st 01. 07. 2009 v 17:21 -0700:
> >> Folks,
> >>
> >> There's been a lot of discussion/argument around how to handle the last
> >> commitfest, but there seems to be a tota
Hi,
Le 2 juil. 09 à 22:20, Kevin Grittner a écrit :
Here's the Makefile contents:
You could compare to this:
http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/backports/uuid-ossp/Makefile?rev=1.1.1.1&content-type=text/x-cvsweb-markup
SHLIB_LINK = -lpoppler -L/usr/local/lib
SHLIB_LINK += $(OSSP
2009/7/3 Jaime Casanova :
> On Fri, Jul 3, 2009 at 12:34 AM, Brendan Jurd wrote:
>> 2009/7/3 Robert Haas :
>>> Also, we're currently missing the reviewer names
>>> due to limitations of the import script; Brendan is fixing this.
>>
>> Update: The reviewer names have now been populated.
>>
>
> looks
On Fri, Jul 3, 2009 at 12:34 AM, Brendan Jurd wrote:
> 2009/7/3 Robert Haas :
>> Also, we're currently missing the reviewer names
>> due to limitations of the import script; Brendan is fixing this.
>
> Update: The reviewer names have now been populated.
>
looks good... now, how can i mark a patch
2009/7/3 Robert Haas :
> Also, we're currently missing the reviewer names
> due to limitations of the import script; Brendan is fixing this.
Update: The reviewer names have now been populated.
Cheers,
BJ
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to yo
Robert Haas wrote:
On Thu, Jul 2, 2009 at 10:45 PM, KaiGai Kohei wrote:
Right now, I think it is preferable to focus on the first three patches
at the first commit fest.
What's your opinion?
If the first three patches are the least amount of code that makes a
complete feature, then that's the
On Thu, 2 Jul 2009, Robert Haas wrote:
I think it's important to clarify the distinction between when a
committer is planning to look at the patch but maybe somebody else
should too, and when the committer is planning to take exclusive
responsibility for the patch and nobody else should bother
Hi,
On Fri, Jul 3, 2009 at 2:01 PM, Robert Haas wrote:
> My preference for ease of CommitFest management would be one thread on
> -hackers for each chunk that can be separately reviewed and committed.
> So if there are three severable chunks here, send a patch for each
> one with a descriptive su
On Thu, Jul 2, 2009 at 10:45 PM, KaiGai Kohei wrote:
> Right now, I think it is preferable to focus on the first three patches
> at the first commit fest.
>
> What's your opinion?
If the first three patches are the least amount of code that makes a
complete feature, then that's the right way to go
On Fri, Jul 3, 2009 at 12:32 AM, Fujii Masao wrote:
> Hi,
>
> On Fri, Jul 3, 2009 at 11:02 AM, Robert Haas wrote:
>> On Tue, Jun 16, 2009 at 2:13 AM, Fujii Masao wrote:
>>> The attached latest patch provides this capability. You can easily set up
>>> the
>>> synch rep according to the following pr
Per Dave Page's request of this morning, my CommitFest management
application now has a real hostname (see subject line). I have also
sent Dave an email with details of the install process and location of
files, per his request (let me know if there's somewhere else those
details should be posted)
Hi,
On Fri, Jul 3, 2009 at 11:59 AM, Alvaro
Herrera wrote:
> WRT the signal handling piece, I remember something in that area being
> committed and then reverted because it had issues. Does this version
> fix those issues? (Assuming it's the same patch)
Yes. After the patch was reverted, Heikki
Hi,
On Fri, Jul 3, 2009 at 11:02 AM, Robert Haas wrote:
> On Tue, Jun 16, 2009 at 2:13 AM, Fujii Masao wrote:
>> The attached latest patch provides this capability. You can easily set up the
>> synch rep according to the following procedure.
>> http://wiki.postgresql.org/wiki/NTT%27s_Development_P
Robert Haas wrote:
2009/6/30 KaiGai Kohei :
The SE-PostgreSQL patches are updated as follows:
01) http://sepgsql.googlecode.com/files/sepgsql-01-sysatt-8.4-r2096.patch
02) http://sepgsql.googlecode.com/files/sepgsql-02-core-8.4-r2096.patch
03) http://sepgsql.googlecode.com/files/sepgsql-03-gram
Robert Haas escribió:
> Second, I am wondering whether Heikki feels that it would be useful to
> assign round-robin reviewers for this patch, or whether he's going to
> be the principal reviewer himself. We could assign either a reviewer
> (or reviewers) to the whole patch, or we could assign rev
On Thu, Jul 2, 2009 at 3:42 PM, Zdenek Kotala wrote:
>
> Josh Berkus píše v st 01. 07. 2009 v 17:21 -0700:
>> Folks,
>>
>> There's been a lot of discussion/argument around how to handle the last
>> commitfest, but there seems to be a total consensus that we want to have
>> the first CF on July 15th
On Thu, Jul 2, 2009 at 10:02 PM, Robert Haas wrote:
> Second, I am wondering whether Heikki feels that it would be useful to
> assign round-robin reviewers for this patch, or whether he's going to
> be the principal reviewer himself. We could assign either a reviewer
> (or reviewers) to the whole
On Tue, Jun 16, 2009 at 2:13 AM, Fujii Masao wrote:
> The attached latest patch provides this capability. You can easily set up the
> synch rep according to the following procedure.
> http://wiki.postgresql.org/wiki/NTT%27s_Development_Projects#How_to_set_up_Synch_Rep
This patch no longer applies
2009/6/30 KaiGai Kohei :
> The SE-PostgreSQL patches are updated as follows:
>
> 01) http://sepgsql.googlecode.com/files/sepgsql-01-sysatt-8.4-r2096.patch
> 02) http://sepgsql.googlecode.com/files/sepgsql-02-core-8.4-r2096.patch
> 03) http://sepgsql.googlecode.com/files/sepgsql-03-gram-8.4-r2096.pa
On Thu, Jul 2, 2009 at 5:50 PM, Greg Stark wrote:
> So I currently have some free time as I'm currently between jobs. I
> can start going through the queued patches in the next few weeks.
> Should I be looking at the wiki currently? Or is your tool ready to
> go?
Wiki for now. Brendan Jurd is wor
Tom Lane wrote:
> Peter Eisentraut writes:
> > On Friday 19 June 2009 00:56:42 Bruce Momjian wrote:
> >> A third install method is to use PGXS
> >> (assuming the new 'pg_config' is in your $PATH):
> >>
> >> USE_PGXS=1 gmake prefix=/usr/local/pgsql.new install
>
> > Maybe the latter method should
Peter Eisentraut wrote:
> On Friday 19 June 2009 00:56:42 Bruce Momjian wrote:
>
> > > The makefile for pg_migrator currently assumes by default that it is
> > > located under contrib/. Which confuses me.
> >
> > You can compile pg_migrator by copying it to /contrib, or using PGXS;
> > both work.
Jaime Casanova writes:
> We want to use the same format/sections like in the TODO?
Sure, why not? Just copy the page and strip out the not-done items.
No reason to think hard here.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
On Thu, Jul 2, 2009 at 4:50 PM, Tom Lane wrote:
> Alvaro Herrera writes:
>> Jaime Casanova wrote:
>>> I guess todo items marked as [D] (Done) should be removed now... right?
>
>> Would there be some value in creating a new page TodoDone84 and moving
>> those items to it?
>
> In the past we've figu
Andrew Dunstan wrote:
>
>
> Joshua D. Drake wrote:
>> On Thu, 2009-07-02 at 17:29 -0400, Alvaro Herrera wrote:
>>
>>> Jaime Casanova wrote:
>>>
I guess todo items marked as [D] (Done) should be removed now... right?
>>> Would there be some value in creating a new page TodoD
So I currently have some free time as I'm currently between jobs. I
can start going through the queued patches in the next few weeks.
Should I be looking at the wiki currently? Or is your tool ready to
go?
--
greg
http://mit.edu/~gsstark/resume.pdf
--
Sent via pgsql-hackers mailing list (pgsql-
Alvaro Herrera writes:
> Jaime Casanova wrote:
>> I guess todo items marked as [D] (Done) should be removed now... right?
> Would there be some value in creating a new page TodoDone84 and moving
> those items to it?
In the past we've figured that old TODO versions could be retrieved
from CVS his
Joshua D. Drake wrote:
On Thu, 2009-07-02 at 17:29 -0400, Alvaro Herrera wrote:
Jaime Casanova wrote:
Hi,
I guess todo items marked as [D] (Done) should be removed now... right?
Would there be some value in creating a new page TodoDone84 and moving
those items to it?
F
Andrew Dunstan wrote:
>
>
> Alvaro Herrera wrote:
>> Hi,
>>
>> I was having a look at this snippet:
>> http://wiki.postgresql.org/wiki/Google_Translate
>> and it turns out that it doesn't work if the result contains non-ASCII
>> chars. Does anybody know how to fix it?
>>
>> alvherre=# select gtran
"Kevin Grittner" writes:
> Does it seem likely that fixing these issues will allow PGXS to work?
Couldn't say. It would be useful to compare ldd output for
pdftotext.so built both ways.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.
On Thu, 2009-07-02 at 17:29 -0400, Alvaro Herrera wrote:
> Jaime Casanova wrote:
> > Hi,
> >
> > I guess todo items marked as [D] (Done) should be removed now... right?
>
> Would there be some value in creating a new page TodoDone84 and moving
> those items to it?
For historical record I could s
Alvaro Herrera wrote:
Hi,
I was having a look at this snippet:
http://wiki.postgresql.org/wiki/Google_Translate
and it turns out that it doesn't work if the result contains non-ASCII
chars. Does anybody know how to fix it?
alvherre=# select gtranslate('en', 'es', 'he');
ERROR: plpython: fun
Jaime Casanova wrote:
> Hi,
>
> I guess todo items marked as [D] (Done) should be removed now... right?
Would there be some value in creating a new page TodoDone84 and moving
those items to it?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company
Hi,
I guess todo items marked as [D] (Done) should be removed now... right?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
Tom Lane wrote:
> "Kevin Grittner" writes:
>> PG_CPPFLAGS =-I/usr/include/poppler -shared -fpic
>> SHLIB_LINK = -lpoppler -L/usr/local/lib
>
> It doesn't seem appropriate to put -shared or -fpic into
> PG_CPPFLAGS. If you need those, the makefiles should add them
> automatically.
>
> The other
"Kevin Grittner" writes:
> PG_CPPFLAGS =-I/usr/include/poppler -shared -fpic
> SHLIB_LINK = -lpoppler -L/usr/local/lib
It doesn't seem appropriate to put -shared or -fpic into PG_CPPFLAGS.
If you need those, the makefiles should add them automatically.
The other thing that seems peculiar is look
Hi,
I was having a look at this snippet:
http://wiki.postgresql.org/wiki/Google_Translate
and it turns out that it doesn't work if the result contains non-ASCII
chars. Does anybody know how to fix it?
alvherre=# select gtranslate('en', 'es', 'he');
ERROR: plpython: function "gtranslate" could n
I've been wondering whether anyone else would want to use the
functions we wrote to extract text from PDF documents stored in bytea
columns. If so, I would need to sort out the problems I've been
having with builds through the PGXS techniques. Here's the directory,
after a successful build under
Josh Berkus píše v st 01. 07. 2009 v 17:21 -0700:
> Folks,
>
> There's been a lot of discussion/argument around how to handle the last
> commitfest, but there seems to be a total consensus that we want to have
> the first CF on July 15th.
Can we add flags like bump catalog version, bump page l
Peter Eisentraut writes:
> On Friday 19 June 2009 00:56:42 Bruce Momjian wrote:
>> A third install method is to use PGXS
>> (assuming the new 'pg_config' is in your $PATH):
>>
>> USE_PGXS=1 gmake prefix=/usr/local/pgsql.new install
> Maybe the latter method should be the default, as it matches b
Tom Lane píše v čt 02. 07. 2009 v 13:13 -0400:
> I wrote:
> > Yes. What I was thinking of doing was committing a configure change to
> > reject flex < 2.5.31, and waiting to see how much of the buildfarm goes
> > red.
>
> Actually, most of the buildfarm members show which flex version they are
>
Tom Lane píše v čt 02. 07. 2009 v 11:32 -0400:
> Andrew Dunstan writes:
> > Tom Lane wrote:
> >> Right, this will only affect people doing development or otherwise
> >> building from a CVS pull.
>
> > Of course, that includes the whole buildfarm. We might need to ask some
> > people to upgrade
Peter Eisentraut writes:
> Looks good, but needs documentation and tab-complete.c updates, it seems.
> And
> you should revisit this patch to make it consistent with the S flag that was
> added to most \d commands. For example, \dL would show only user-added
> languages, but \dLS would inclu
On Monday 02 February 2009 15:29:51 Fernando Ike wrote:
> Hi,
>
> On Fri, Jan 30, 2009 at 3:03 PM, Fernando Ike wrote:
> > Hi,,
> >
> >My job, I maintainer some postgres server for clients. We have
> > many PL/(Java, Perl, Ruby, Python, R) and to more easy
> > administration, I worked new lit
gsst...@mit.edu (Greg Stark) writes:
> I would like to propose a different strategy. Instead of always
> tackling all the smaller patches and leaving the big patches for last,
> I would suggest we start with Hot Standby.
>
> In fact I would suggest as Hot Standby has already gotten a first pass
> r
... is now the required version to rebuild configure.
Other than that, nothing changes.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Alvaro Herrera wrote:
> I wonder why we have two ways at all (I'm not counting the stuff
> about copying it to contrib because it seems pointless). The other
> day I was looking at orafce code in pgfoundry, and at clearxlogtail
> too IIRC, and they both had the "ifdef USE_PGXS" stuff in the
>
Peter Eisentraut wrote:
> On Friday 19 June 2009 00:56:42 Bruce Momjian wrote:
>
> > > The makefile for pg_migrator currently assumes by default that it is
> > > located under contrib/. Which confuses me.
> >
> > You can compile pg_migrator by copying it to /contrib, or using PGXS;
> > both work.
On Thu, Jul 2, 2009 at 12:48 PM, Euler Taveira de
Oliveira wrote:
> I know that it didn't solve the estimation problem but ... IMHO the
> [under|over]estimation should be treated by an external tool (autoexplain?).
> So when we enable the query progress and some node reports a difference
> between
On Friday 19 June 2009 00:56:42 Bruce Momjian wrote:
> > The makefile for pg_migrator currently assumes by default that it is
> > located under contrib/. Which confuses me.
>
> You can compile pg_migrator by copying it to /contrib, or using PGXS;
> both work. Read the 15-step install instruction
On Thu, Jul 2, 2009 at 1:10 PM, Joshua Tolley wrote:
> On Thu, Jul 02, 2009 at 03:42:56PM +0100, Dave Page wrote:
>> On Thu, Jul 2, 2009 at 3:22 PM, Joshua Tolley wrote:
>> > On Thu, Jul 02, 2009 at 08:41:27AM +0100, Dave Page wrote:
>> >> As far as I'm aware, there's been no code
>> >> review yet
Peter Eisentraut wrote:
> make distprep is what prepares those files.
Perfect! Flex files built. No errors. Thanks much!
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Thu, Jul 2, 2009 at 12:13 PM, Tom Lane wrote:
> However I'm a bit worried about the situation for Windows --- does
> anyone know whether a newer flex is readily available for Windows?
>
MSYS Suplementary Tools (for mingw) includes flex-2.5.33
http://sourceforge.net/projects/mingw/files/
--
At
On Thursday 02 July 2009 19:46:04 Tom Lane wrote:
> "Kevin Grittner" writes:
> > Then I take it back -- the new flex versions would have little or no
> > impact on me. Worst case, I might need to download a snapshot to
> > apply my patch for testing on the "big" machines. If I understood
> > wha
Tom Lane wrote:
> "Kevin Grittner" writes:
>> jade -D . -d stylesheet.dsl -i output-text -t sgml -V nochunks
>> tempfile_HISTORY.sgml >HISTORY.html
>> /bin/sh: jade: not found
>
> Looks like you're missing openjade. However, that's only used to
> produce the HISTORY file which is hardly cr
"Kevin Grittner" writes:
> I seem to be able to "sneak up on it from behind" by doing a regular
> make and then "make distclean" and copying the results. Perhaps
> someone knows off-hand what I'm missing that prevents "make dist" from
> working. The attempt ends with:
> jade -D . -d styleshee
Tom Lane wrote:
> Peter or Marc could clue you in a bit better, but I think it's as
> simple as saying "make dist" at the top level of a modified source
> tree. This gets you a source tarball the same way the release
> tarballs are made.
I seem to be able to "sneak up on it from behind" by d
I wrote:
> Yes. What I was thinking of doing was committing a configure change to
> reject flex < 2.5.31, and waiting to see how much of the buildfarm goes
> red.
Actually, most of the buildfarm members show which flex version they are
running in the configure output. A quick look shows that of
On Thu, Jul 02, 2009 at 03:42:56PM +0100, Dave Page wrote:
> On Thu, Jul 2, 2009 at 3:22 PM, Joshua Tolley wrote:
> > On Thu, Jul 02, 2009 at 08:41:27AM +0100, Dave Page wrote:
> >> As far as I'm aware, there's been no code
> >> review yet either, which would probably be a good idea.
> >
> > I don'
"Kevin Grittner" writes:
> Then I take it back -- the new flex versions would have little or no
> impact on me. Worst case, I might need to download a snapshot to
> apply my patch for testing on the "big" machines. If I understood
> what make options I could use on my machine to create derived f
On Wed, 2009-07-01 at 11:19 -0400, Caleb Cushing wrote:
> I'd like to see this topic revisited since as far as I can see it
> hasn't been seriously discussed in years. I believe the main arguments
> against are why do we need more more numeric datatypes and increased
> maintenance. It would seem t
Alvaro Herrera wrote:
> Yes, the snapshots have the derived files too.
Then I take it back -- the new flex versions would have little or no
impact on me. Worst case, I might need to download a snapshot to
apply my patch for testing on the "big" machines. If I understood
what make options I
Robert Haas writes:
> On Thu, Jul 2, 2009 at 11:39 AM, Greg Stark wrote:
>> Someone doing a CVS pull already needs a specific recent version of
>> autoconf anyways. How old is this version of flex compared to the
>> version of autoconf we require?
> Really? configure is in CVS, so I don't think
On Thu, Jul 2, 2009 at 11:39 AM, Greg Stark wrote:
>>> Tom Lane wrote:
Right, this will only affect people doing development or otherwise
building from a CVS pull.
>
> Someone doing a CVS pull already needs a specific recent version of
> autoconf anyways. How old is this version of flex c
>> Tom Lane wrote:
>>> Right, this will only affect people doing development or otherwise
>>> building from a CVS pull.
Someone doing a CVS pull already needs a specific recent version of
autoconf anyways. How old is this version of flex compared to the
version of autoconf we require?
--
greg
ht
On Thu, Jul 2, 2009 at 11:05 AM, Dickson S. Guedes wrote:
> Em Thu, 02 Jul 2009 00:15:22 -0300, Robert Haas
> escreveu:
>>
>> The main problem is that my fine software only contains test data at
>> this point. If we have any volunteers who are available to migrate
>> the information from the Wiki
Kevin Grittner wrote:
> Alvaro Herrera wrote:
>
> > Keep in mind that if you build from a tarball, the lexer has already
> > been run elsewhere and you don't need flex.
>
> Does that hold for the daily snapshots? If so, I should be good.
Yes, the snapshots have the derived files too.
--
A
Andrew Dunstan writes:
> Tom Lane wrote:
>> Right, this will only affect people doing development or otherwise
>> building from a CVS pull.
> Of course, that includes the whole buildfarm. We might need to ask some
> people to upgrade there.
Yes. What I was thinking of doing was committing a co
Alvaro Herrera wrote:
> Keep in mind that if you build from a tarball, the lexer has already
> been run elsewhere and you don't need flex.
Does that hold for the daily snapshots? If so, I should be good. My
workstation is OK on flex version. (I run kubuntu on my desktop.)
-Kevin
--
Sen
Tom Lane wrote:
Alvaro Herrera writes:
Kevin Grittner wrote:
Tom Lane wrote:
Since 2.5.33 is now over three years old, this does not seem like an
onerous requirement, but I thought I'd better ask if anyone has an
objection?
You'd be causing problems for SuSE Enterp
Alvaro Herrera writes:
> Kevin Grittner wrote:
>> Tom Lane wrote:
>>> Since 2.5.33 is now over three years old, this does not seem like an
>>> onerous requirement, but I thought I'd better ask if anyone has an
>>> objection?
>>
>> You'd be causing problems for SuSE Enterprise users, like us:
>
"Kevin Grittner" writes:
> kgri...@ccdev-db:/etc/init.d> flex --version
> flex 2.5.31
> Just how broken is the version we're using?
You might want to take that up with SuSE. The flex NEWS file just cites
"numerous bug and security fixes" from .31 to .33.
Our CVS logs show half a dozen changes
Kevin Grittner wrote:
> Tom Lane wrote:
>
> > so the new minimum supported version would probably be 2.5.33
> > (2.5.31 was kinda broken for other reasons, and there was no
> > 2.5.32).
> >
> > Since 2.5.33 is now over three years old, this does not seem like an
> > onerous requirement, but I t
On Thu, Jul 2, 2009 at 12:48 PM, Robert Haas wrote:
> On Thu, Jul 2, 2009 at 7:11 AM, Dave Page wrote:
>> Suggest a suitable name by which we can address the service (we don't
>> use the internal names like coridan because things can get moved
>> around), and I can set that up in a few minutes.
>
>
Tom Lane wrote:
Andrew Dunstan writes:
I think it would need to be benchmarked. My faint recollection is that
the re-entrant lexers are slower.
The flex documentation states in so many words:
The option `--reentrant' does not affect the performance of the scanner.
Do you f
Em Thu, 02 Jul 2009 00:15:22 -0300, Robert Haas
escreveu:
The main problem is that my fine software only contains test data at
this point. If we have any volunteers who are available to migrate
the information from the Wiki to my app (which will involve a fair
amount of legwork), then I recomm
Andrew Dunstan writes:
> I think it would need to be benchmarked. My faint recollection is that
> the re-entrant lexers are slower.
The flex documentation states in so many words:
The option `--reentrant' does not affect the performance of the scanner.
Do you feel a need to verify thei
"Kevin Grittner" wrote:
> Tom Lane wrote:
>
>> so the new minimum supported version would probably be 2.5.33
We still have five SuSE Enterprise 9 boxes in use as database servers;
while we've got someone tasked with replacing them, I wonder if that
version is so dead that we want to abandon
I have simple solution
http://www.sai.msu.su/~megera/wiki/2008-12-17
On Thu, 2 Jul 2009, Hans-Juergen Schoenig -- PostgreSQL wrote:
hello,
i made a small patch which i found useful for my personal tasks.
it would be nice to see this in 8.5. if not core then maybe contrib.
it transforms a tsv
On Thu, Jul 2, 2009 at 10:13 AM, Hans-Juergen Schoenig --
PostgreSQL wrote:
> hello,
>
> i made a small patch which i found useful for my personal tasks.
> it would be nice to see this in 8.5. if not core then maybe contrib.
> it transforms a tsvector to table format which is really nice for text
>
On Thu, Jul 2, 2009 at 3:22 PM, Joshua Tolley wrote:
> On Thu, Jul 02, 2009 at 08:41:27AM +0100, Dave Page wrote:
>> As far as I'm aware, there's been no code
>> review yet either, which would probably be a good idea.
>
> I don't have loads of time in the coming days, but IIRC I've taken a glance a
Tom Lane wrote:
> so the new minimum supported version would probably be 2.5.33
> (2.5.31 was kinda broken for other reasons, and there was no
> 2.5.32).
>
> Since 2.5.33 is now over three years old, this does not seem like an
> onerous requirement, but I thought I'd better ask if anyone has an
Tom Lane wrote:
I'd like to return to the project I suggested here:
http://archives.postgresql.org/message-id/18653.1239741...@sss.pgh.pa.us
of getting rid of plpgsql's private lexer and having it use the core
lexer instead. This will require making the core lexer re-entrant,
which is not poss
hello,
i made a small patch which i found useful for my personal tasks.
it would be nice to see this in 8.5. if not core then maybe contrib.
it transforms a tsvector to table format which is really nice for text
processing and comparison.
test=# SELECT * FROM tsvcontent(to_tsvector('english',
I'd like to return to the project I suggested here:
http://archives.postgresql.org/message-id/18653.1239741...@sss.pgh.pa.us
of getting rid of plpgsql's private lexer and having it use the core
lexer instead. This will require making the core lexer re-entrant,
which is not possible with our oldest
On Thu, Jul 02, 2009 at 08:41:27AM +0100, Dave Page wrote:
> As far as I'm aware, there's been no code
> review yet either, which would probably be a good idea.
I don't have loads of time in the coming days, but IIRC I've taken a glance at
a past version of the code, and would be willing to do so
Em Thu, 02 Jul 2009 00:26:14 -0300, Brendan Jurd
escreveu:
I imagine that "migration" would basically be converting the wiki data
into SQL, so I would need the database schema underlying the new CF
app.
How about parsing wiki content and create a "migration script" based on
pgcommitfest table
On Thu, Jul 2, 2009 at 2:42 AM, Peter Eisentraut wrote:
> On Thursday 02 July 2009 05:29:58 Robert Haas wrote:
>> If you are taking a look at
>> any of the patches submitted for this CommitFest, please put your name
>> next to them on the wiki. Please ALSO add a comment saying something
>> like "t
On Thu, Jul 2, 2009 at 2:32 AM, Bruce Momjian wrote:
> I think the only resonable solution would be to consider the estimated
> cost of each node and then compute what percentage complete each node
> is.
>
Well you can do better for some nodes. A sequential scan for example
can tell you exactly wh
On Thu, Jul 2, 2009 at 7:11 AM, Dave Page wrote:
> On Thu, Jul 2, 2009 at 12:04 PM, Robert Haas wrote:
>> On Jul 2, 2009, at 3:41 AM, Dave Page wrote:
>>
>>> On Thu, Jul 2, 2009 at 1:21 AM, Josh Berkus wrote:
>>>
Robert, I have not reviewed your software. Do I need a login or
something?
On Thu, Jul 2, 2009 at 12:04 PM, Robert Haas wrote:
> On Jul 2, 2009, at 3:41 AM, Dave Page wrote:
>
>> On Thu, Jul 2, 2009 at 1:21 AM, Josh Berkus wrote:
>>
>>> Robert, I have not reviewed your software. Do I need a login or
>>> something?
>>
>> It's not in productions yet as It's not been docum
On Jul 2, 2009, at 3:41 AM, Dave Page wrote:
On Thu, Jul 2, 2009 at 1:21 AM, Josh Berkus wrote:
Robert, I have not reviewed your software. Do I need a login or
something?
It's not in productions yet as It's not been documented or given a
public hostname/servicename, both of which are requ
On Thu, Jul 2, 2009 at 1:21 AM, Josh Berkus wrote:
> Robert, I have not reviewed your software. Do I need a login or something?
It's not in productions yet as It's not been documented or given a
public hostname/servicename, both of which are requirements for any
postgresql.org services. As far a
94 matches
Mail list logo
