Re: [HACKERS] schema_to_xmlschema() seems a bit less than finished

when a column gets removed from a table as a result of drop cascade, the tuple descriptor (more specifically rel->rd_att field) for that relation is not updated properly? regards, -- Sibte Abbas EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)

Re: [HACKERS] [GENERAL] 8.2.4 signal 11 with large transaction

_server_log() function in elog.c? thanks, -- Sibte Abbas EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [HACKERS] [GENERAL] 8.2.4 signal 11 with large transaction

tters/2007-07/msg00215.php Makes sense. regards, -- Sibte Abbas EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

[HACKERS] TODO item: add \# which lists line numbers, and allows command execution

. Comments are welcomed. regards, -- Sibte Abbas

Re: [HACKERS] TODO item: add \# which lists line numbers, and allows command execution

On 9/8/07, Sibte Abbas <[EMAIL PROTECTED]> wrote: > > > Hi all, > > Realizing that the mentioned TODO item discussed at > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php > <http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php> can

Re: [HACKERS] Raw device I/O for large objects

ld be highly appreciated! > http://www.postgresql.org/docs/techdocs http://www.postgresql.org/docs/faq/ The postgresql documentation: http://www.postgresql.org/docs/8.2/interactive/index.html Also, If you have the source, the src/tools/backend directory has some useful material for starter

Re: [HACKERS] NULL and plpgsql rows

know what tuple descriptor it will actually contain, however, maybe we can have "special" tuple descriptors for un-assigned record types. For example, if for NULL/unassigned record type we create a tuple descriptor of "VOID" type, and then initialize its corresponding (one

Re: [HACKERS] [PATCHES] psql slash# command

diately executing it. Actual execution is only a away, > but this definition would allow you to edit the command a bit more > before you execute it --- including \e to use an editor. It also > closes the loop in terms of providing some confidence that you typed > the number you should have typed. > This makes more sense and also appears to be much safer. I will start modifying the patch as per this approach now. regards, -- Sibte Abbas

Re: [HACKERS] psql slash# command

gt; > New patch submitted: http://archives.postgresql.org/pgsql-patches/2008-04/msg00240.php regards, -- Sibte Abbas