Hi,
On 05/28/15 13:25, birimblongas wrote:
Hi,
My app was working just fine. A month ago postmaster started to eat all my
cpu sometimes (not all day, but a lot of times and everyday) and then my app
gets really slow and sometimes don't even complete the requests.
What could it be?
A lot of t
Hi,
My app was working just fine. A month ago postmaster started to eat all my
cpu sometimes (not all day, but a lot of times and everyday) and then my app
gets really slow and sometimes don't even complete the requests.
What could it be?
--
View this message in context:
http://postgresql.nab
Tomas Vondra writes:
> Why exactly does the second query use a much slower plan I'm not sure. I
> believe I've found an issue in planning semi joins (reported to
> pgsql-hackers a few minutes ago), but may be wrong and the code is OK.
I think you are probably right that there's a bug there: the
Hi,
On 05/30/15 15:46, Ashik S L wrote:
We are using postgres SQL version 8.4.17..
FYI 8.4 is already unsupported for ~1 year, so you should consider
upgrading to a newer release. Also, the newest version in that branch is
8.4.22, so with 8.4.17 you're missing ~1 year of patches.
Postgres
We are using postgres SQL version 8.4.17..
Postgres DB szie is 900 MB and we are inserting 273 rows at once .and
each row is of 60 bytes.Every time we insert 16380 bytes of data.
I tried to make some config changes using above link. But I did not
see any improvement.
I made following changes in pos
