Re: [HACKERS] Minor bug in src/port/rint.c

Bruce Momjian <[EMAIL PROTECTED]> writes: > Added to TODO: > o Fix port/rint.c to be spec-compliant Actually, the TODO I had in mind was entirely not that. Getting exact spec compliance in a completely platform-independent fashion is probably impossible, and is certainly not worth the tro

Re: [HACKERS] [GSoC] (Is it OK to choose items without % mark in theToDoList) && (is it an acceptable idea to build index on Flash Disk)

Alvaro Herrera <[EMAIL PROTECTED]> writes: > mx escribió: >> In my opinion, we have to change Access Method and some part of Storage >> Managers greatly. Is it too hard for a beginner to serve as a GSoC project? > It's like 3 orders of magnitude more work than I'd expect a Postgres > newbie to b

Re: [HACKERS] [GSoC] (Is it OK to choose items without % mark in theToDoList) && (is it an acceptable idea to build index on Flash Disk)

mx escribió: > In my opinion, we have to change Access Method and some part of Storage > Managers greatly. Is it too hard for a beginner to serve as a GSoC project? It's like 3 orders of magnitude more work than I'd expect a Postgres newbie to be able to finish in a summer. -- Alvaro Herrera

Re: [HACKERS] [GSoC] (Is it OK to choose items without % mark in theToDoList) && (is it an acceptable idea to build index on Flash Disk)

On Tue, 25 Mar 2008, mx wrote: The atom unit of flash is page(512~2048byte typically). Page are organized into blocks, typically of 32 or 64 pages. All read write and write operations happen at page granularity, but erase operations happen at block granularity. You made a subtle switch here

Re: [HACKERS] RFC: array_agg() per SQL:200n

Add to TODO: * Add SQL-standard array_agg() and unnest() array functions http://archives.postgresql.org/pgsql-hackers/2008-01/msg01017.php --- Neil Conway wrote: > I recently noticed that SQL:200n[1] defines a new aggre

Re: [HACKERS] pl/pgsql Plan Invalidation and search_path

Add to pl/pgsql TODO: o Consider invalidating the cache or keeping seperate cached copies when search_path changes http://archives.postgresql.org/pgsql-hackers/2008-01/msg01009.php --- Tom Lane

Re: [HACKERS] Bug in psql/enum

Added to psql TODO: o Improve display if enums http://archives.postgresql.org/pgsql-hackers/2008-01/msg00826.php --- David Fetter wrote: > Folks, > > 8.3's psql is ponderously unhelpful when getting the

Re: [HACKERS] Minor bug in src/port/rint.c

Added to TODO: o Fix port/rint.c to be spec-compliant http://archives.postgresql.org/pgsql-hackers/2008-01/msg00808.php --- Mark Cave-Ayland wrote: > Hi everyone, > > I believe that there is a small bug

Re: [HACKERS] postgresql in FreeBSD jails: proposal

Added to TODO: * Improve detection of shared memory segments being used by other FreeBSD jails http://archives.postgresql.org/pgsql-hackers/2008-01/msg00656.php --- Mischa Sandberg wrote: > Here (@sophos.com) we run m

Re: [HACKERS] [GSoC] (Is it OK to choose items without % mark in theToDoList) && (is it an acceptable idea to build index on Flash Disk)

Thank you for your suggestion! > The biggest problem with the hash index is currently that there's no > significant performance over b-tree. If you want to work on hash > indexes, I would suggest doing benchmarking and looking at ways to > improve performance, before spending time on making it mul

Re: [HACKERS] [pgsql-www] New email list for emergency communications

bruce wrote: > Gregory Stark wrote: > > "Bruce Momjian" <[EMAIL PROTECTED]> writes: > > > > > You can get the message-ids by grep'ing the mbox file, and the comments > > > are all: > > > > > > http://js-kit.com/rss/momjian.us/msgid-* > > > > > > e.g. > > > > > > http://js-kit.com/rss/momjian.u

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Gregory Stark wrote: > "Bruce Momjian" <[EMAIL PROTECTED]> writes: > > > You can get the message-ids by grep'ing the mbox file, and the comments > > are all: > > > > http://js-kit.com/rss/momjian.us/msgid-* > > > > e.g. > > > > http://js-kit.com/rss/momjian.us/[EMAIL PROTECTED] > > Huh, f

Re: [HACKERS] [pgsql-www] New email list for emergency communications

"Bruce Momjian" <[EMAIL PROTECTED]> writes: > You can get the message-ids by grep'ing the mbox file, and the comments > are all: > > http://js-kit.com/rss/momjian.us/msgid-* > > e.g. > > http://js-kit.com/rss/momjian.us/[EMAIL PROTECTED] Huh, fascinating. it's actually an RSS feed. I

Re: [HACKERS] xlogdump

Added to TODO: * Move pgfoundry's xlogdump to /contrib and have it rely more closely on the WAL backend code http://archives.postgresql.org/pgsql-hackers/2007-11/msg00035.php --- Gregory Stark wrote: > > There's an x

Re: [HACKERS] count(*) performance improvement ideas

Pavan Deolasee wrote > On Thu, Mar 20, 2008 at 3:24 AM, Stephen Denne > <[EMAIL PROTECTED]> wrote: > > > > > Pavan also refers to deferred triggers, which has got me > thinking about another possible solution: > > > > Instead of inserting a delta row, that will be updated a > lot of times, cre

Re: [HACKERS] Recovery of Multi-stage WAL actions

Added to TODO: > * Have resource managers report the duration of their status changes > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg01468.php --- Simon Riggs wrote: > We've had two hard to diagnose errors i

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Alvaro Herrera wrote: > Bruce Momjian wrote: > > > > If we modify the archives to have a URL to go straight to a message-id and > > > Bruce generated a list all on one page including comments and message-ids > > > then > > > I could process them all into a wiki page in a few hours. > > > > Ideal

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Bruce Momjian wrote: > > If we modify the archives to have a URL to go straight to a message-id and > > Bruce generated a list all on one page including comments and message-ids > > then > > I could process them all into a wiki page in a few hours. > > Ideally we could have a message id link to

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Gregory Stark wrote: > "Bruce Momjian" <[EMAIL PROTECTED]> writes: > > >> I tried this once already. I dumped the first page of Bruce's queue into a > >> wiki page and laid it out in a column. But I wanted to add links back to > >> the > >> messages in the archive and ran into a problem with that

Re: [HACKERS] PANIC caused by open_sync on Linux

Added to TODO: * Be more aggressive about creating WAL files http://archives.postgresql.org/pgsql-hackers/2007-10/msg01325.php --- Tom Lane wrote: > Greg Smith <[EMAIL PROTECTED]> writes: > > On Fri, 26 Oct 2007, ITAGAK

Re: [HACKERS] [pgsql-www] New email list for emergency communications

"Bruce Momjian" <[EMAIL PROTECTED]> writes: >> I tried this once already. I dumped the first page of Bruce's queue into a >> wiki page and laid it out in a column. But I wanted to add links back to the >> messages in the archive and ran into a problem with that. It also would have >> been a pain b

Re: [HACKERS] Proposal: generate_iterator functions

I see you just submitted the patch so we will address it after the commit fest --- thanks. --- Pavel Stehule wrote: > done > > http://www.pgsql.cz/index.php/Iter%C3%A1tor_pole > > I'll send patch later > > Pavel > > 2007

Re: [HACKERS] dblink un-named connection doesn't get re-used

Add to TODO: * Have /contrib/dblink reuse unnamed connections http://archives.postgresql.org/pgsql-hackers/2007-10/msg00895.php --- Decibel! wrote: > Is it intentional that dblink's unnamed connections don't get re-used

Re: [HACKERS] Deprecating heap_formtuple/heap_modifytuple/heap_deformtuple

Added to TODO: * Remove old-style routines for manipulating tuples http://archives.postgresql.org/pgsql-hackers/2007-10/msg00851.php --- Gregory Stark wrote: > > I think we should go ahead and kill the old 'n'/' ' api

Re: [HACKERS] 8.4 TODO item: make src/port support libpq and ecpg directly

Added to TODO: * Create three versions of libpgport to simplify client code http://archives.postgresql.org/pgsql-hackers/2007-10/msg00154.php --- Tom Lane wrote: > This business with having libpq and ecpg pull in src/po

Re: [HACKERS] proposal casting from XML[] to int[], numeric[], text[]

Added to TODO: * Allow xml arrays to be cast to other data types http://archives.postgresql.org/pgsql-hackers/2007-09/msg00981.php http://archives.postgresql.org/pgsql-hackers/2007-10/msg00231.php http://archives.postgresql.org/pgsql-hackers/2007-11/msg00471.php

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Tom Lane wrote: > Gregory Stark <[EMAIL PROTECTED]> writes: > > Am i looking at the right list though? The one I'm looking at still starts > > with a patch to which Tom commented "This is superseded by a later > > submission" > > which I think has been there since pretty much the start of the comm

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Gregory Stark wrote: > > > "Bruce Momjian" <[EMAIL PROTECTED]> writes: > > > Alvaro Herrera wrote: > >> > >> I'm not sure I follow. I tried last week to give some hours for patch > >> review. What actually happened was that I had to wade through a ton of > >> stuff, skipping patches that were

Re: [HACKERS] Proposal: new ereport option "errdetail_log"

Alvaro Herrera <[EMAIL PROTECTED]> writes: > Gregory Stark wrote: >> The axis on which I still see real room for improvement here is on the >> description of the locks. It's awfully hard for a user to tell from the >> deadlock message exactly what operation of the query was acquiring what lock >> w

Re: [HACKERS] Proposal: new ereport option "errdetail_log"

Gregory Stark wrote: > The axis on which I still see real room for improvement here is on the > description of the locks. It's awfully hard for a user to tell from the > deadlock message exactly what operation of the query was acquiring what lock > when it deadlocked. Are the involved queries not

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Gregory Stark <[EMAIL PROTECTED]> writes: > Am i looking at the right list though? The one I'm looking at still starts > with a patch to which Tom commented "This is superseded by a later submission" > which I think has been there since pretty much the start of the commitfest. Yeah, there is still

Re: [HACKERS] [pgsql-www] New email list for emergency communications

"Bruce Momjian" <[EMAIL PROTECTED]> writes: > Alvaro Herrera wrote: >> >> I'm not sure I follow. I tried last week to give some hours for patch >> review. What actually happened was that I had to wade through a ton of >> stuff, skipping patches that were already applied, threads that were >>

Re: [HACKERS] Table rewrites vs. pending AFTER triggers

Hi, I'm with David on this one. Transactional DDL also turns out to be incredibly helpful for tools that generate and load DDL to extend the database, for example triggers and control tables to implement reliable messaging. You can put the setup in a single transaction, which vastly simplifies t

Re: [HACKERS] Proposal: new ereport option "errdetail_log"

"Tom Lane" <[EMAIL PROTECTED]> writes: > Gregory Stark <[EMAIL PROTECTED]> writes: >> I wonder how useful it is to output process ids at all. And for that matter >> whether leaking process ids alone could be considered a security risk. > > Seems overly paranoid, especially considering we've output

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Alvaro Herrera wrote: Also I don't know what patches we have for the next commitfest. I would gladly give some time to put up a Wiki page to list the patches for the next commitfest. Would that be helpful? Yes. My experience is similar to yours. I'm not prepared to spend hours perusin

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Alvaro Herrera wrote: > Bruce Momjian wrote: > > Alvaro Herrera wrote: > > > > I did manage to find actual patches, but I had then to resort to my own > > > mailbox to get the actual patch to apply and review. > > > > You can download an mbox of the entire queue if that helps. > > Ah, yeah, that

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > >> Also I don't know what patches we have for the next commitfest. I would > >> gladly give some time to put up a Wiki page to list the patches for the > >> next commitfest. Would that be helpful? > > > Uh, I don't think we have any p

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Bruce Momjian wrote: > Alvaro Herrera wrote: > > I did manage to find actual patches, but I had then to resort to my own > > mailbox to get the actual patch to apply and review. > > You can download an mbox of the entire queue if that helps. Ah, yeah, that's what I did. > > Also I don't know w

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Bruce Momjian <[EMAIL PROTECTED]> writes: >> Also I don't know what patches we have for the next commitfest. I would >> gladly give some time to put up a Wiki page to list the patches for the >> next commitfest. Would that be helpful? > Uh, I don't think we have any patches for the next commit f

Re: [HACKERS] gcc 4.3 breaks ContribCheck in 8.2 and older.

On Mon, Mar 24, 2008 at 05:59:33PM -0400, Tom Lane wrote: > Kurt Roeckx <[EMAIL PROTECTED]> writes: > > I did try the patch. It fails just the same way. > > Hmph. So we still don't know why 8.2 and 8.3 behave differently ... > [ pokes around ... ] Hah, maybe this is it: > > http://archives.post

Re: [HACKERS] Integer datetimes

Zdenek Kotala <[EMAIL PROTECTED]> writes: > Tom Lane napsal(a): >> This is not happening, at least not without 100 times more work than >> anyone has shown willingness to put into the issue. > I understand your arguments, but it is important for in-place upgrade. No, it is not, you merely need to

Re: [HACKERS] gcc 4.3 breaks ContribCheck in 8.2 and older.

Kurt Roeckx <[EMAIL PROTECTED]> writes: > I did try the patch. It fails just the same way. Hmph. So we still don't know why 8.2 and 8.3 behave differently ... [ pokes around ... ] Hah, maybe this is it: http://archives.postgresql.org/pgsql-committers/2007-03/msg00292.php

[HACKERS] Commit fest status

FYI, we started the commit fest with 2k emails. We now have 787 emails left to process, and many are done but waiting for me to add TODO items or just delete them. -- Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us EnterpriseDB http://postgres.enterpri

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Alvaro Herrera wrote: > Bruce Momjian wrote: > > > This is an interesting observation that deserves to be discussed > > separately, and relates to the patch queue. Many people want to know > > what is happening with the patch queue but having better reporting > > doesn't seem to help much the peo

Re: [HACKERS] Problem with site doc search

Gurjeet Singh wrote: On Thu, Mar 6, 2008 at 5:01 PM, Gevik Babakhani <[EMAIL PROTECTED] > wrote: > No, it's still on the TODO. Gevik has also been looking a bit > at it (I think - at least he's indicated that he is), and he > recently got some new parser

Re: [HACKERS] Integer datetimes

Tom Lane napsal(a): Zdenek Kotala <[EMAIL PROTECTED]> writes: The result will be two datatypes datetime and timestamp_int or timestamp_float. This is not happening, at least not without 100 times more work than anyone has shown willingness to put into the issue. It seems fairly clear that eve

Re: [HACKERS] gcc 4.3 breaks ContribCheck in 8.2 and older.

On Mon, Mar 24, 2008 at 03:52:09PM -0400, Tom Lane wrote: > Kurt Roeckx <[EMAIL PROTECTED]> writes: > > On Mon, Mar 24, 2008 at 02:52:18PM -0400, Tom Lane wrote: > >> Please try that patch and see what it fixes pre-8.3. > > > No, returnValue contains the same value for both 8.2 and 8.3. There is

Re: [HACKERS] gcc 4.3 breaks ContribCheck in 8.2 and older.

Kurt Roeckx <[EMAIL PROTECTED]> writes: > On Mon, Mar 24, 2008 at 02:52:18PM -0400, Tom Lane wrote: >> Please try that patch and see what it fixes pre-8.3. > No, returnValue contains the same value for both 8.2 and 8.3. There is > no reason why casting from a char * to a char * should result into

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Bruce Momjian wrote: > This is an interesting observation that deserves to be discussed > separately, and relates to the patch queue. Many people want to know > what is happening with the patch queue but having better reporting > doesn't seem to help much the people who are actually processing th

Re: [HACKERS] [pgsql-www] New email list for emergency communications

Stefan Kaltenbrunner wrote: [ Discussion about making infrastructure downtime more visible to people.] > > Right now, when email is down, I just start IM'ing people. A more > > structured system would help me. > > Some people would say a more structured approach to patch/bug tracking > would h

Re: [HACKERS] gcc 4.3 breaks ContribCheck in 8.2 and older.

On Mon, Mar 24, 2008 at 02:52:18PM -0400, Tom Lane wrote: > Kurt Roeckx <[EMAIL PROTECTED]> writes: > > 8.2 and 8.3 actually get the same value in fmgr_oldstyle(), it just > > seems they do something else with it somewhere else. > > Doh. I'll bet the difference is this fix: > > http://archives.p

Re: [HACKERS] gcc 4.3 breaks ContribCheck in 8.2 and older.

Kurt Roeckx <[EMAIL PROTECTED]> writes: > 8.2 and 8.3 actually get the same value in fmgr_oldstyle(), it just > seems they do something else with it somewhere else. Doh. I'll bet the difference is this fix: http://archives.postgresql.org/pgsql-committers/2007-07/msg00131.php Please try that pat

Re: [HACKERS] gcc 4.3 breaks ContribCheck in 8.2 and older.

On Mon, Mar 24, 2008 at 03:05:31PM -0300, Alvaro Herrera wrote: > Kurt Roeckx wrote: > > > No, this has nothing to do with CFLAGS. It's calling a function which > > returns something other than it actually returns. > > Yeah but apparently gcc 4.3 is working in 8.3 and later. What happens > to y

Re: [HACKERS] [PATCHES] Eliminate more detoast copies for packed varlenas

Added to TODO: * Research reducing deTOASTing in more places http://archives.postgresql.org/pgsql-hackers/2007-09/msg00895.php --- Gregory Stark wrote: > "Tom Lane" <[EMAIL PROTECTED]> writes: > > > Gregory Stark <[EMA

Re: [HACKERS] gcc 4.3 breaks ContribCheck in 8.2 and older.

Alvaro Herrera wrote: Kurt Roeckx wrote: No, this has nothing to do with CFLAGS. It's calling a function which returns something other than it actually returns. Yeah but apparently gcc 4.3 is working in 8.3 and later. What happens to your sample program if you compile it with the

Re: [HACKERS] gcc 4.3 breaks ContribCheck in 8.2 and older.

Kurt Roeckx wrote: > No, this has nothing to do with CFLAGS. It's calling a function which > returns something other than it actually returns. Yeah but apparently gcc 4.3 is working in 8.3 and later. What happens to your sample program if you compile it with the CFLAGS used in 8.3 versus those

Re: [HACKERS] gcc 4.3 breaks ContribCheck in 8.2 and older.

On Mon, Mar 24, 2008 at 02:05:14PM -0300, Alvaro Herrera wrote: > Kurt Roeckx wrote: > > On Thu, Mar 20, 2008 at 06:53:27PM -0400, Tom Lane wrote: > > > Kurt Roeckx <[EMAIL PROTECTED]> writes: > > > > I did some tests with gcc 4.3 on the branches from 7.4 to 8.3 and head. > > > > 8.3 and head don't

Re: [HACKERS] FW: was [PERFORM] partitioned table and ORDER BY indexed_field DESC LIMIT 1

Patch rejected because of Tom Lane's comments: > This is useless since it does not represent a complete patch; the > provided code calls a lot of Greenplum-private routines that weren't > provided. It's not even reviewable let alone a candidate to apply.

Re: [HACKERS] Reducing Transaction Start/End Contention

Thread URL added to TODO: * SMP scalability improvements --- Paul van den Bogaard wrote: > Just started a blog session on my findings running Postgres 8.3(beta) > on a mid range Sun Fire server. Second entry is ab

Re: [HACKERS] Straightforward changes for increased SMP scalability

Add to TODO: * SMP scalability improvements http://archives.postgresql.org/pgsql-hackers/2007-07/msg00439.php --- Simon Riggs wrote: > David Strong presented some excellent results of his SMP scalability > testing at Ot

Re: [HACKERS] Straightforward changes for increased SMP scalability

Added to TODO: * SMP scalability improvements http://archives.postgresql.org/pgsql-hackers/2007-07/msg00439.php --- Simon Riggs wrote: > David Strong presented some excellent results of his SMP scalability > testing at

Re: [HACKERS] Proposal: new ereport option "errdetail_log"

Gregory Stark <[EMAIL PROTECTED]> writes: > I wonder how useful it is to output process ids at all. And for that matter > whether leaking process ids alone could be considered a security risk. Seems overly paranoid, especially considering we've output that information after a deadlock for many yea

Re: [HACKERS] gcc 4.3 breaks ContribCheck in 8.2 and older.

Kurt Roeckx wrote: > On Thu, Mar 20, 2008 at 06:53:27PM -0400, Tom Lane wrote: > > Kurt Roeckx <[EMAIL PROTECTED]> writes: > > > I did some tests with gcc 4.3 on the branches from 7.4 to 8.3 and head. > > > 8.3 and head don't have a problem. All others failed in the > > > ContribCheck state. > >

Re: [HACKERS] [GSoC] (Is it OK to choose items without % mark in theToDoList) && (is it an acceptable idea to build index on Flash Disk)

"Heikki Linnakangas" <[EMAIL PROTECTED]> writes: > mx wrote: >> By the way, I'm writing proposal for multi-column hash now. > The biggest problem with the hash index is currently that there's no > significant performance over b-tree. If you want to work on hash > indexes, I would suggest doing b

Re: [HACKERS] Proposal: new ereport option "errdetail_log"

"Tom Lane" <[EMAIL PROTECTED]> writes: > I'm not sure how many people noticed this -patches discussion: > http://archives.postgresql.org/pgsql-patches/2008-03/msg00282.php > so I'm reposting on -hackers. > > The conclusion I drew from that thread is that we should send the text > of all queries in

Re: [HACKERS] Bug in libpq causes local clients to hang

"Jeffrey Baker" <[EMAIL PROTECTED]> writes: > The stack trace doesn't actually make sense, does it? I think that > (at least) the PQmblen frame is spurious. Yeah, it's obviously lying to some extent. I think you need a copy of libpq with debug symbols enabled to get a more accurate trace.

Re: [PATCHES] [HACKERS] Show INHERIT in \du

"Brendan Jurd" <[EMAIL PROTECTED]> writes: > I've had a chance to look at this now, and although it certainly does > seem workable, there's a lot of duplication of code that I feel uneasy > about. describeOneTableDetails essentially already duplicates the > table buildling code in printQuery, so I

Re: [HACKERS] Bug in libpq causes local clients to hang

On Mon, Mar 24, 2008 at 9:24 AM, Tom Lane <[EMAIL PROTECTED]> wrote: > "Jeffrey Baker" <[EMAIL PROTECTED]> writes: > > On Sun, Mar 23, 2008 at 8:35 PM, Tom Lane <[EMAIL PROTECTED]> wrote: > > >> If it works over TCP and not over Unix socket, it's a kernel bug. > >> The libpq code doesn't really k

Re: [PATCHES] [HACKERS] Show INHERIT in \du

On 21/03/2008, Tom Lane <[EMAIL PROTECTED]> wrote: > "Brendan Jurd" <[EMAIL PROTECTED]> writes: > > We can't just build the output table by hand like > > describeOneTableDetails does? Admittedly it's kludgy, but it's not an > > unprecedented kludge. > > > Oh, I had forgotten the existence of tha

Re: [HACKERS] Bug in libpq causes local clients to hang

"Jeffrey Baker" <[EMAIL PROTECTED]> writes: > On Sun, Mar 23, 2008 at 8:35 PM, Tom Lane <[EMAIL PROTECTED]> wrote: >> If it works over TCP and not over Unix socket, it's a kernel bug. >> The libpq code doesn't really know the difference after connection >> setup. > The same thought occurred to me,

Re: [HACKERS] [GSoC] (Is it OK to choose items without % mark in theToDoList) && (is it an acceptable idea to build index on Flash Disk)

mx wrote: Hello,Everyone! I'm a student in China. and I'm preparing for GSocC2008 in these days. There are two questions about GSoC. 1. There's a paragraph about the Example Proposal Ideas in PostgreSQL Summer Projects website. *TODO Items*: A number of the items on our TODO list have been mark

[HACKERS] Proposal: new ereport option "errdetail_log"

I'm not sure how many people noticed this -patches discussion: http://archives.postgresql.org/pgsql-patches/2008-03/msg00282.php so I'm reposting on -hackers. The conclusion I drew from that thread is that we should send the text of all queries involved in a deadlock to the server log, regardless

Re: [HACKERS] Bug in libpq causes local clients to hang

On Sun, Mar 23, 2008 at 8:35 PM, Tom Lane <[EMAIL PROTECTED]> wrote: > "Jeffrey Baker" <[EMAIL PROTECTED]> writes: > > You'll note that I'm using the DBD::Pg Perl interface. So far I've > > never seen this happen with TCP connections, only with UNIX sockets. > > If it works over TCP and not ove

Re: [HACKERS] Better error message for select_common_type()

Added to TODO: * Improve reporting of UNION type mismatches http://archives.postgresql.org/pgsql-hackers/2007-04/msg00944.php http://archives.postgresql.org/pgsql-hackers/2008-03/msg00597.php --- Peter Eisentraut wrot

Re: [HACKERS] gcc 4.3 breaks ContribCheck in 8.2 and older.

On Thu, Mar 20, 2008 at 06:53:27PM -0400, Tom Lane wrote: > Kurt Roeckx <[EMAIL PROTECTED]> writes: > > I did some tests with gcc 4.3 on the branches from 7.4 to 8.3 and head. > > 8.3 and head don't have a problem. All others failed in the > > ContribCheck state. > > > You can see the results on

[HACKERS] [GSoC] (Is it OK to choose items without % mark in theToDoList) && (is it an acceptable idea to build index on Flash Disk)

Hello,Everyone! I'm a student in China. and I'm preparing for GSocC2008 in these days. There are two questions about GSoC. 1. There's a paragraph about the Example Proposal Ideas in PostgreSQL Summer Projects website. *TODO Items*: A number of the items on our TODO list have been marked as > good

Re: [HACKERS] pg_dump additional options for performance

Alvaro Herrera wrote: > Bruce Momjian wrote: > > > > Added to TODO: > > > > o Allow pre/data/post files when dumping a single object, for > > performance reasons > > > > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php > > "When dumping a single obje

Re: [HACKERS] Problem with site doc search

On Thu, Mar 6, 2008 at 5:01 PM, Gevik Babakhani <[EMAIL PROTECTED]> wrote: > > No, it's still on the TODO. Gevik has also been looking a bit > > at it (I think - at least he's indicated that he is), and he > > recently got some new parser code to look at to see if we can > > use to fix it. > > > >

Re: [HACKERS] Project idea for Google Summer of Code

Hello On 24/03/2008, Дмитрий Кириллов <[EMAIL PROTECTED]> wrote: > Hello, hackers! > > I have very simple (but IMHO very progressive) idea for Google SoC project: > > My idea is to add package (and "package group") concepts to PL/pgSQL & Packages are really important. Two notes: a) PostgreSQL i

[HACKERS] Project idea for Google Summer of Code

Hello, hackers! I have very simple (but IMHO very progressive) idea for Google SoC project: My idea is to add package (and "package group") concepts to PL/pgSQL & to front-end such functionality with a special Mono project for PostgreSQL server-side development. This functionality may help m