According to
http://www.postgresql.org/docs/9.2/static/storage-file-layout.html
"When a table or index exceeds 1 GB, it is divided into gigabyte-sized
segments. The first segment's file name is the same as the filenode;
subsequent segments are named filenode.1, filenode.2, etc."
I was wondering w
On 04/20/2013 04:30 PM, Daniel Cristian Cruz wrote:
2013/4/20 Adrian Klaver mailto:adrian.kla...@gmail.com>>
On 04/20/2013 04:08 PM, Daniel Cristian Cruz wrote:
I think I didn't make it clear: the session memory usage is
growing up
too fast, until all server memor
2013/4/20 Adrian Klaver
> On 04/20/2013 04:08 PM, Daniel Cristian Cruz wrote:
>
>> I think I didn't make it clear: the session memory usage is growing up
>> too fast, until all server memory got used and swap occurs.
>>
>> Never saw something like that. The version is under a test enviroment
>> f
On 04/20/2013 04:08 PM, Daniel Cristian Cruz wrote:
I think I didn't make it clear: the session memory usage is growing up
too fast, until all server memory got used and swap occurs.
Never saw something like that. The version is under a test enviroment
for a long time...
Thanks if someone could
I think I didn't make it clear: the session memory usage is growing up too
fast, until all server memory got used and swap occurs.
Never saw something like that. The version is under a test enviroment for a
long time...
Thanks if someone could help me.
2013/4/20 Daniel Cristian Cruz
> Hi all,
Hi all,
I've upgrade from 9.1.4 to 9.2.4, and got some very weird issue.
My server got connections with RES (column from top utility) with too much
memory:
top - 19:50:58 up 384 days, 23:55, 2 users, load average: 4.28, 6.51, 7.68
Tasks: 417 total, 1 running, 416 sleeping, 0 stopped, 0 z
On Apr 20, 2013, at 18:27, Scott Parkerson wrote:
> I ran into this issue where an update command with a bad subquery in the
> WHERE clause still ran and updated everything as if there was no WHERE clause
> at all. Needless to say, it was a bit surprising. o_O
Nope, the query parser is fine.
Y
On 2013-04-15, dinesh kumar wrote:
> --047d7b675e70cee73c04da61865c
> Content-Type: text/plain; charset=ISO-8859-1
>
> Dear Sirs,
>
> Apologizes, if this is a duplicate question.
>
> Would like to request you to share your valuable inputs on this. I would
> like to know the PostgreSQL registry ent
Hi,
2013/04/21 0:01, Mike Levine wrote:
According
tohttp://www.postgresql.org/docs/9.2/static/storage-file-layout.html
"When a table or index exceeds 1 GB, it is divided into gigabyte-sized
segments. The first segment's file name is the same as the filenode;
subsequent segments are named fileno
I ran into this issue where an update command with a bad subquery in the
WHERE clause still ran and updated everything as if there was no WHERE
clause at all. Needless to say, it was a bit surprising. o_O
I've created a test (see below) that demonstrates what I think is to be the
issue; it's self-
According to
http://www.postgresql.org/docs/9.2/static/storage-file-layout.html
"When a table or index exceeds 1 GB, it is divided into gigabyte-sized
segments. The first segment's file name is the same as the filenode;
subsequent segments are named filenode.1, filenode.2, etc."
I was wondering w
thanks,i have resolved the problem.
change to kernel-headers-2.6.32-358.2.1.el6.i686 is ok.
-- --
??: "Tom Lane";
: 2013??4??17??(??) 0:08
??: "Alvaro Herrera";
: "wk"<304702...@qq.com>; "pgsql-general";
: Re: [GENERAL]
12 matches
Mail list logo