Re: [HACKERS] [GENERAL] Transaction eating up all RAM

Has there been any progress on this? Is it a TODO? --- Tom Lane wrote: > "Peter Zeltins" <[EMAIL PROTECTED]> writes: > > On my laptop (WinXP, PG 8.1.1, ActivePerl 5.8.7) it eats up around > > 1M/second - ran it for ~10 min

Re: [HACKERS] plperl on AIX

In an attempt to throw the authorities off his trail, [EMAIL PROTECTED] (John F Rizzo) transmitted: > I posted this in other lists with no response...  Can anyone help? > I'm having trouble getting plperl to work on AIX 5.3.2. > Postgresql Version: 8.1.1 > Perl Version: 5.8.7 > I've rebuilt perl a

Re: [HACKERS] obtaining row locking information

> Tatsuo Ishii wrote: > > > Tatsuo, are you planning to add this to CVS HEAD? > > > > Yes, I would like to add if there's no objection. > > I have heard no comment, and it looks useful, so please add it at your > convenience. Ok, done. -- Tatsuo Ishii SRA OSS, Inc. Japan > -

Re: [HACKERS] obtaining row locking information

Tatsuo Ishii wrote: > > Tatsuo, are you planning to add this to CVS HEAD? > > Yes, I would like to add if there's no objection. I have heard no comment, and it looks useful, so please add it at your convenience. --- > -- >

Re: [HACKERS] obtaining row locking information

> Tatsuo, are you planning to add this to CVS HEAD? Yes, I would like to add if there's no objection. -- Tatsuo Ishii SRA OSS, Inc. Japan > --- > > Tatsuo Ishii wrote: > > I have attached pgrowlocks tested under current. > >

Re: [HACKERS] Question about the MemoryContext

Thank you :) On Sat, 2006-04-22 at 18:16 -0400, Tom Lane wrote: > Gevik Babakhani <[EMAIL PROTECTED]> writes: > > Could someone please explain the MemoryContext switching. For example > > MemoryContextSwitchTo function. How does this work? > > src/backend/utils/mmgr/README might help. It's somew

Re: [HACKERS] Question about the MemoryContext

Gevik Babakhani <[EMAIL PROTECTED]> writes: > Could someone please explain the MemoryContext switching. For example > MemoryContextSwitchTo function. How does this work? src/backend/utils/mmgr/README might help. It's somewhat pointed at people who've already been hacking the backend, but I think

Re: [PATCHES] [HACKERS] Automatically setting work_mem

On Sat, Apr 22, 2006 at 01:49:25PM -0700, David Fetter wrote: > On Sat, Apr 22, 2006 at 01:14:42PM -0700, David Gould wrote: > > > To avoid running out of swap and triggering the oom killer we have > > had to reduce work_mem below what we prefer. > > Dunno about your work_mem, but you can make su

[HACKERS] Question about the MemoryContext

Could someone please explain the MemoryContext switching. For example MemoryContextSwitchTo function. How does this work? ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings

Re: [PATCHES] [HACKERS] Automatically setting work_mem

On Sat, Apr 22, 2006 at 01:14:42PM -0700, David Gould wrote: > To avoid running out of swap and triggering the oom killer we have > had to reduce work_mem below what we prefer. Dunno about your work_mem, but you can make sure the OOM killer doesn't kill you as follows

Re: [PATCHES] [HACKERS] Automatically setting work_mem

On Sat, Apr 22, 2006 at 06:38:53PM +0100, Simon Riggs wrote: > On Sat, 2006-04-22 at 13:17 -0400, Tom Lane wrote: > > Simon Riggs <[EMAIL PROTECTED]> writes: > > > I still do, for multi-user systems. Releasing unused memory from a large > > > CREATE INDEX will allow that memory to be swapped out, e

Re: [PATCHES] [HACKERS] Automatically setting work_mem

On Sat, 2006-04-22 at 13:17 -0400, Tom Lane wrote: > Simon Riggs <[EMAIL PROTECTED]> writes: > > I still do, for multi-user systems. Releasing unused memory from a large > > CREATE INDEX will allow that memory to be swapped out, even if the brk > > point can't be changed. > > Say what? It can get

Re: [HACKERS] TODO items..

OK, done. --- Tom Lane wrote: > Bruce Momjian writes: > > but that was not clear. TODO is now: > > o Fix psql's \dn for various schema combinations (Neil) > > http://archives.postgresql.org/pgsql-hackers/

Re: [HACKERS] TODO items..

Bruce Momjian writes: > but that was not clear. TODO is now: > o Fix psql's \dn for various schema combinations (Neil) > http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php > with a URL that has the details. Thanks for pointing out the problem. You might want to

Re: [PATCHES] [HACKERS] Automatically setting work_mem

On Sat, Apr 22, 2006 at 01:17:08PM -0400, Tom Lane wrote: > Simon Riggs <[EMAIL PROTECTED]> writes: > > I still do, for multi-user systems. Releasing unused memory from a large > > CREATE INDEX will allow that memory to be swapped out, even if the brk > > point can't be changed. > > Say what? It

Re: [PATCHES] [HACKERS] Automatically setting work_mem

Simon Riggs <[EMAIL PROTECTED]> writes: > I still do, for multi-user systems. Releasing unused memory from a large > CREATE INDEX will allow that memory to be swapped out, even if the brk > point can't be changed. Say what? It can get "swapped out" anyway, whether we free() it or not. More to th

Re: [HACKERS] TODO items..

Dhanaraj M wrote: > I saw the following in the TODO list. I am currently trying to work on them. > I could not understand clearly what needs to be done. Can anybody give me > the details for the following so that I can work on? > > clients-psql > = > 1. Have psql show current values for a

Re: [HACKERS] TODO items..

On Sat, Apr 22, 2006 at 05:37:28PM +0200, Gevik Babakhani wrote: > > > This one means when you do a \dt of a sequence, add a column to display > > the current value. > > > > Perhaps this one will be tricky because you will never be sure to get > the last sequence number when you query for it. Th

Re: [HACKERS] TODO items..

> This one means when you do a \dt of a sequence, add a column to display > the current value. > Perhaps this one will be tricky because you will never be sure to get the last sequence number when you query for it. The number could change the moment the query is finished. -

Re: [HACKERS] TODO items..

Dhanaraj M wrote: > I saw the following in the TODO list. I am currently trying to work on them. > I could not understand clearly what needs to be done. Can anybody give me > the details for the following so that I can work on? > > clients-psql > = > 1. Have psql show current values for a

Re: [HACKERS] obtaining row locking information

Tatsuo, are you planning to add this to CVS HEAD? --- Tatsuo Ishii wrote: > I have attached pgrowlocks tested under current. > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > > > Tatsuo, have you developed a new version of this f

Re: [PATCHES] [HACKERS] Automatically setting work_mem

On Fri, 2006-04-21 at 23:07 -0400, Bruce Momjian wrote: > Where are we on this patch? Well the patches work and have been performance tested, with results posted. Again, the title of this thread doesn't precisely describe the patch any longer. The question is do people believe there is benefit in

[HACKERS] TODO items..

I saw the following in the TODO list. I am currently trying to work on them. I could not understand clearly what needs to be done. Can anybody give me the details for the following so that I can work on? clients-psql = 1. Have psql show current values for a sequence 2. Fix psql's display