Robert Haas writes:
>>> ... The affected patches are:
>>> - Listen/Notify Rewrite.
>>> - Writeable CTEs.
>>> - more frame options for window functions
>>> - knngist
>>> - rbtree
> I think it might be time to revisit this issue. SR is in, and we have
> a week left in the CF, and we have all of th
On Sun, 2010-02-07 at 00:18 -0500, Robert Haas wrote:
> Jeff, do you think this patch is ready for committer? If so, please
> mark it as such on commitfest.postgresql.org - otherwise, please
> clarify what you think the action items are.
I'll post an update tomorrow.
Regards,
Jeff Davis
On Fri, 2010-02-05 at 09:19 -0500, Bruce Momjian wrote:
> My son has brought to my attention that our current crop of Python
> client libraries is inadequate/confusing. I took a look myself, and
> asked on our IRC channel, and am now convinced this area needs
> attention.
I have written up a set
Robert,
> I think it might be time to revisit this issue. SR is in, and we have
> a week left in the CF, and we have all of the above patches plus 5
> small ones left to deal with. rbtree is close to being committable, I
> think; knngist has not been reviewed yet; you (Tom) have claimed the
> fr
On Thu, Jan 7, 2010 at 10:20 PM, Tom Lane wrote:
> Robert Haas writes:
>> OK, we have a proposal on the table to bump some patches from this
>> CommitFest to free up more committer resources, particularly Tom, to
>> work on Hot Standby and Streaming Replication and attempt to
>> accelerate the pr
On Wed, Feb 3, 2010 at 4:34 AM, Joachim Wieland wrote:
> On Wed, Feb 3, 2010 at 2:05 AM, Jeff Davis wrote:
>>> Thanks, very well spotted... Actually the same is true for LISTEN... I
>>> have reworked the patch to do the changes to listenChannels only in
>>> the post-commit functions.
>>
>> I'm wo
On Sat, Feb 6, 2010 at 7:03 AM, Andres Freund wrote:
> On Saturday 06 February 2010 06:03:30 Greg Smith wrote:
>> Andres Freund wrote:
>> > On 02/03/10 14:42, Robert Haas wrote:
>> >> Well, maybe we should start with a discussion of what kernel calls
>> >> you're aware of on different platforms an
On Tue, Feb 2, 2010 at 4:03 AM, Boszormenyi Zoltan wrote:
> Thanks for testing it, with the attached patch your test case also
> returns SELECT N.
Thoughts:
1. Looks like you've falsified the last comment block in PortalRunMulti().
2. I don't like the duplication of code in PortalRun() between t
On Feb 6, 2010, at 5:51 PM, Josh Berkus wrote:
>> Finally, I just don't see the existing (often PG specific) goals that I have
>> in mind for it appealing to the majority of [web framework/abstraction]
>> users.
>
> What are those goals?
I think the most interesting one that has yet to be imple
Kevin,
> Of course all of this is from the perspective of Python users. Of
> course, you have your own features that you want from your end (from
> PostgreSQL's perspective). Perhaps this info would help you to know
> which avenue to pursue.
That's invaluable. Thanks for chiming in!
--Josh Be
I saw this on reddit and thought I might drop a line.
I went through this same issue, trying to find a postgresql driver. Mostly, I
had no intention of using psycopg because of its copyleft licensing. (Of
course, I don't need to go into why.)
Anyways, here's some info that might help on thre
On Sat, Feb 6, 2010 at 7:48 PM, Marko Kreen wrote:
> This is long-term todo item for psycopg, seems offtopic
> to the "driver situation".
[...]
> This is routine bug in either app or psycopg, we have no reason
> to touch it. The guy should report to appropriate lists.
[...]
> Long-term todo item
> Finally, I just don't see the existing (often PG specific) goals that I have
> in mind for it appealing to the majority of [web framework/abstraction] users.
What are those goals?
--Josh Berkus
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your sub
On 2/7/10, Greg Smith wrote:
> Marko Kreen wrote:
> > Psycopg was the leader, especially in web-environments,
> > but it has non-obvious license and with dead website it does not
> > seem that attractive. Although it is well-maintained still.
> > Best path forward would be to talk with Psycopg gu
Greg Smith wrote:
> To summarize what I saw on this thread, the primary wishlist of changes
> to it are:
>
> -License change
> -Consider refactoring to better follow standard driver practices, such
> as using PQExecParams
> -Improvement in transaction control to resolve issues that cause idle
>
Marko Kreen wrote:
The pg8000 / bpgsql seem to be toy projects, and anyway you dont
want to use pure-Python drivers in high-performance environments.
We are not talking about C#/java here.
Right, and the comments from James reinforce this general idea: there
is little value to the people w
Guy Rouillier wrote:
> On 1/6/2010 3:29 PM, Tom Lane wrote:
> > Guy Rouillier writes:
> >> Oracle states clearly in the SQL Reference manual:
> >
> >> "A modifier can appear in a format model more than once. In such a case,
> >> each subsequent occurrence toggles the effects of the modifier."
> >
M Z writes:
> The thing is, why it doesn't crash on 8.3.8 but crash on 8.4.2? Any idea?
Pure luck. Memory-clobber bugs like these are notoriously
nondeterministic. Any minor, logically unrelated change could make them
visible or not visible, because the clobber happens to clobber data that
is o
Robert Haas wrote:
> On Sat, Jan 2, 2010 at 7:47 PM, Tom Lane wrote:
> > Peter Eisentraut writes:
> >> On l?r, 2010-01-02 at 17:34 -0500, Tom Lane wrote:
> >>> As for the overhead, these queries are not zero-maintenance. ?I still
> >>> think that the usefulness of tab completion here is pretty da
The thing is, why it doesn't crash on 8.3.8 but crash on 8.4.2? Any idea? A
patch was applied to 8.3 but not to 8.4.2?
Thanks,
M Z
On Fri, Feb 5, 2010 at 1:45 PM, Robert Haas wrote:
> On Wed, Feb 3, 2010 at 8:49 AM, Alvaro Herrera
> wrote:
> > Robert Haas escribió:
> >> On Mon, Feb 1, 2010 at
I wrote:
> Still fooling with VACUUM FULL on catalogs ... I find that a sanity
> check I put in is barfing on "VACUUM FULL pg_class", because the
> transient table is built with a toast table, whereas pg_class hasn't got
> one. It seems like it probably ought to have one, because either relacl
> o
Peter Eisentraut wrote:
> In 8.3, running \c from a file prints something like
>
> You are now connected to database "postgres".
>
> In 8.4 it prints
>
> psql (8.4.1)
> You are now connected to database "postgres".
>
> Is it intentional/sensible to repeat the startup banner every time the
> con
On Saturday 06 February 2010 17:32:43 Andres Freund wrote:
> On Saturday 06 February 2010 02:25:33 Tatsuo Ishii wrote:
> > Hi,
> >
> > While testing Hot Standby, I have encountered strange behavior with
> > DROP DATABASE command.
> >
> > 1) connect to "test" database at standby via psql
> > 2) is
On Saturday 06 February 2010 02:25:33 Tatsuo Ishii wrote:
> Hi,
>
> While testing Hot Standby, I have encountered strange behavior with
> DROP DATABASE command.
>
> 1) connect to "test" database at standby via psql
> 2) issue DROP DATABASE test command to primary
> 3) session #1 works fine
> 4) c
Fujii Masao wrote:
> On Mon, Jan 4, 2010 at 9:55 PM, Heikki Linnakangas
> wrote:
> > Heikki Linnakangas wrote:
> >> Here's is modified patch that adds a new backupStartPoint field to
> >> pg_control for that + some other minor editorialization.
> >
> > I've committed this now.
>
> Thanks a lot!
>
Kevin Grittner wrote:
> [resend, because of apparent failure to hit the list]
>
> Bruce Momjian wrote:
>
> > I am dismayed that we are using a 16MB file for monitoring archive
> > activity. Can't you use pg_current_xlog_location() and only check
> > for an archive file when that location chan
On Saturday 06 February 2010 06:03:30 Greg Smith wrote:
> Andres Freund wrote:
> > On 02/03/10 14:42, Robert Haas wrote:
> >> Well, maybe we should start with a discussion of what kernel calls
> >> you're aware of on different platforms and then we could try to put an
> >> API around it.
> >
> > I
[resend, because of apparent failure to hit the list]
Bruce Momjian wrote:
> I am dismayed that we are using a 16MB file for monitoring archive
> activity. Can't you use pg_current_xlog_location() and only check
> for an archive file when that location changes?
Hmmm Let me think about
Tom Lane wrote:
> Josh Berkus writes:
>>> Barring objections I'm going to press ahead with completing and
>>> committing this; then in a separate patch remove VACUUM FULL INPLACE.
>
>> Was it our determination that we could remove VFI if we eliminated the
>> system catalogs? I'm fine with it, I
On Fri, 2010-02-05 at 10:35 -0800, Josh Berkus wrote:
> I'm not as concerned about "confusion" as the fact that *all* of the
> various Python drivers suck in different, and crippling, ways. I don't
> care how many drivers we have, as long as we have at least one 1st-class
> driver.
Absolutely.
A
30 matches
Mail list logo
