[BUGS] BUG in postgres mathematic
Postgres-7.0.3-2 RedHat-6.2 SELECT int8(5*27.81*100); 13904 SELECT int4(5*27.81*100); 13905 SELECT int8(27.81*100*5); 13905 -- ó Õ×ÁÖÅÎÉÅÍ, ÷ÁÝÅÎËÏ íÁËÓÉÍ, îÉÖÅÇÏÒÏÄÓËÉÅ ÉÎÆÏÒÍÁÃÉÏÎÎÙÅ ÓÅÔÉ (8312) 30-19-05, 34-00-02, 30-09-73 With best regards, Max Vaschenko, Nizhny Novgorod Information Networks.
[BUGS] postmaster grows
Hi. I have a RedHat Linux 6.2 (kernel 2.2.18pre1 SMP) on Intel platform. Postgres-7.0.3-2 (RPM). It grows. Initially about 5mb it grows to 60-70 mb after 2-3 weeks. I use plpgsql. If it does matter, server have a chrooted area. Postgres is running in root but accessed both from root and from chroot (via hardlinked socket /tmp/.s.PGSQL.5432) Some times ago i upgraded it from 7.0.2 version, that grew too. -- ó Õ×ÁÖÅÎÉÅÍ, ÷ÁÝÅÎËÏ íÁËÓÉÍ, îÉÖÅÇÏÒÏÄÓËÉÅ ÉÎÆÏÒÍÁÃÉÏÎÎÙÅ ÓÅÔÉ (8312) 30-19-05, 34-00-02, 30-09-73 With best regards, Max Vaschenko, Nizhny Novgorod Information Networks.
Re: [BUGS] postmaster grows
Tom Lane wrote: > > Max Vaschenko <[EMAIL PROTECTED]> writes: > > I have a RedHat Linux 6.2 (kernel 2.2.18pre1 SMP) on Intel platform. > > Postgres-7.0.3-2 (RPM). > > It grows. Initially about 5mb it grows to 60-70 mb after 2-3 weeks. > > Is this the *postmaster* that's growing, or an individual backend that > you've kept running for a long time? One backend is running long time (2-3 weeks), but i don't pay attension on it. Growing affected on both postmaster and individual backends (running usually less than 1 minute). After some (2-3 weeks) time both postmaster and all (every) backends take about 60mb memory. > > We've fixed a fair number of memory leaks in the backend since 7.0.*, > but there aren't any known leaks in the postmaster ... May be backend that running long time, causes other postgres processes to grow? > > regards, tom lane -- ó Õ×ÁÖÅÎÉÅÍ, ÷ÁÝÅÎËÏ íÁËÓÉÍ, îÉÖÅÇÏÒÏÄÓËÉÅ ÉÎÆÏÒÍÁÃÉÏÎÎÙÅ ÓÅÔÉ (8312) 30-19-05, 34-00-02, 30-09-73 With best regards, Max Vaschenko, Nizhny Novgorod Information Networks.
Re: [BUGS] postmaster grows
Tom Lane wrote: > > Max Vaschenko <[EMAIL PROTECTED]> writes: > > After some (2-3 weeks) time both postmaster and all (every) backends take > > about 60mb memory. > > Okay, then it is a postmaster leak. The backends are started by fork > from the postmaster, so they'd inherit whatever data memory size the > postmaster currently has. > > > May be backend that running long time, causes other postgres processes > > to grow? > > Not possible for a backend to affect the postmaster like that, AFAICS. > I think it's just a garden-variety memory leak in some postmaster > operation. > > Since this isn't being reported by other folks, either there's a > system-specific problem or you are using a postmaster feature that's not > widely used. RedHat 6.2 is pretty common so we can probably eliminate > system-specific issues. Which authentication method(s) do you use? > (If you could send your whole pg_hba.conf file, that might be useful to > look at.) - pg_hba.conf -- local all password host all127.0.0.1255.255.255.255 password host allxxx.xx.x.xx 255.255.255.255 password host allxxx.xx.x.xx 255.255.255.255 password host allxxx.xx.x.xx 255.255.255.255 password host allxxx.xx.x.xx 255.255.255.255 password Four databases with some simple plpgsql triggers. Access to postgres from C and PHP3. > > regards, tom lane -- ó Õ×ÁÖÅÎÉÅÍ, ÷ÁÝÅÎËÏ íÁËÓÉÍ, îÉÖÅÇÏÒÏÄÓËÉÅ ÉÎÆÏÒÍÁÃÉÏÎÎÙÅ ÓÅÔÉ (8312) 30-19-05, 34-00-02, 30-09-73 With best regards, Max Vaschenko, Nizhny Novgorod Information Networks.
[BUGS] BUG or feature?
Hi. Bug or feature? CREATE FUNCTION upd (text, text) RETURNS text AS ' BEGIN RETURN $1; END ' LANGUAGE 'plpgsql'; SELECT upd('aaa','bbb'); aaa SELECT upd(null,'bbb'); All seems ok, but how about next ? SELECT upd('aaa',null); -- ó Õ×ÁÖÅÎÉÅÍ, ÷ÁÝÅÎËÏ íÁËÓÉÍ, îÉÖÅÇÏÒÏÄÓËÉÅ ÉÎÆÏÒÍÁÃÉÏÎÎÙÅ ÓÅÔÉ (8312) 30-19-05, 34-00-02, 30-09-73 With best regards, Max Vaschenko, Nizhny Novgorod Information Networks.