On Sun, Feb 13, 2011 at 9:57 AM, Kevin Grittner wrote:
> Keith Gabryelski wrote:
>
> > here is an example of one process's growth over time --
> >
> > USER PID %CPU %MEMVSZ RSS
> > postgres 20533 0.0 0.3 647388 52216
> > [...]
> > p
I've noticed my postgres processes have been increasing their memory usage.
this seems to happen because my clients applications are using connection
pooling and
until one of the clients forces a connection reset the postgres process does
not
release its memory.
I'd love to understand how to manag
create table tmp
(
id serial not null primary key,
name text,
age integer
);
insert into tmp (name,age) values ('keith', 43),('leslie', 40),('bexley',
19),('casey', 6);
update tmp
set age = data_table.age
from
(
select 'keith'::text as name, 44::integer as age
union
select 'leslie', 5
I'm interested in using pg_migrator to upgrade between postgres server 8.3
and 8.4 on a database
about 4G in size.
In addition, I'd like to move from a 32bit centos os (currently running the
8.3 server) to 64 bit centos os (running a 64bit arch 8.4 server).
Will pg_migrator handle this?
Pax, Kei
