On 11/14/2012 01:56 PM, Wu Ming wrote:
> This is interesting. About the "virtual size of one of the process",
> which process I should look up? Is the one who has the biggest virtual
> size?
Thinking about this some more, I haven't checked to see if Windows adds
dirtied shared_buffers to the proc
Hi,
> As I said, it just isn't that simple when shared memory is involved. A
> rough measure for PostgreSQL is the "virtual size" of one of the
> processes, plus the working sets of all the others. Alternately, you can
> reasonably estimate the memory consumption by adding all the working
> sets a
On 11/13/2012 10:12 PM, Denis wrote:
Please don't think that I'm trying to nitpick here, but pg_dump has options
for dumping separate tables and that's not really consistent with the idea
that "pg_dump is primarily designed for dumping entire databases".
Sure it is. The word "primarily" is
On Tue, Nov 13, 2012 at 7:12 PM, Denis wrote:
> Jeff Janes wrote
>> On Thu, Nov 8, 2012 at 1:04 AM, Denis <
>
>> socsam@
>
>> > wrote:
>>>
>>> Still I can't undesrtand why pg_dump has to know about all the tables?
>>
>> Strictly speaking it probably doesn't need to. But it is primarily
>> designe
Jeff Janes wrote
> On Thu, Nov 8, 2012 at 1:04 AM, Denis <
> socsam@
> > wrote:
>>
>> Still I can't undesrtand why pg_dump has to know about all the tables?
>
> Strictly speaking it probably doesn't need to. But it is primarily
> designed for dumping entire databases, and the efficient way to d
On Tue, Nov 13, 2012 at 2:43 PM, Jeff Janes wrote:
> On Tue, Nov 13, 2012 at 12:03 PM, Jon Nelson
> wrote:
>> On Tue, Nov 13, 2012 at 1:27 PM, Heikki Linnakangas
>> wrote:
>>>
>>> On 13.11.2012 21:13, Jon Nelson wrote:
>>>
>>> I'd guess it's lock contention on WALInsertLock. That means, th
Please reply to the list, not directly to me. Comments follow in-line.
On 11/13/2012 11:37 PM, Wu Ming wrote:
> Hi,
>
> What column in Process Explorer to determine memory usage? Currently I
> thought "Working Set" is the correct one.
As I said, it just isn't that simple when shared memory is invo
On Tue, Nov 13, 2012 at 12:03 PM, Jon Nelson wrote:
> On Tue, Nov 13, 2012 at 1:27 PM, Heikki Linnakangas
> wrote:
>>
>> On 13.11.2012 21:13, Jon Nelson wrote:
>>>
>>
>> I'd guess it's lock contention on WALInsertLock. That means, the system is
>> experiencing lock contention on generating WAL re
On Tue, Nov 13, 2012 at 1:27 PM, Heikki Linnakangas wrote:
> On 13.11.2012 21:13, Jon Nelson wrote:
>
>> I was working on a data warehousing project where a fair number of files
>> could be COPY'd more or less directly into tables. I have a somewhat nice
>> machine to work with, and I ran on 75%
On Tue, Nov 13, 2012 at 11:13 AM, Jon Nelson wrote:
> I was working on a data warehousing project where a fair number of files
> could be COPY'd more or less directly into tables. I have a somewhat nice
> machine to work with, and I ran on 75% of the cores I have (75% of 32 is
> 24).
>
> Performan
On 13.11.2012 21:13, Jon Nelson wrote:
I was working on a data warehousing project where a fair number of files
could be COPY'd more or less directly into tables. I have a somewhat nice
machine to work with, and I ran on 75% of the cores I have (75% of 32 is
24).
Performance was pretty bad. With
I was working on a data warehousing project where a fair number of files
could be COPY'd more or less directly into tables. I have a somewhat nice
machine to work with, and I ran on 75% of the cores I have (75% of 32 is
24).
Performance was pretty bad. With 24 processes going, each backend (in COP
On 12/11/12 22:06, Rafał Rzepecki wrote:
This indeed works around the issue. Thanks!
On Mon, Nov 12, 2012 at 9:53 AM, ashutosh durugkar wrote:
Hey Rafal,
SELECT * FROM (SELECT run_id, utilization FROM stats) AS s WHERE
run_id IN (SELECT run_id FROM runs WHERE server_id = 515);
could you t
13 matches
Mail list logo
