On Fri, 14 Aug 2009, Scott Carey wrote:
The memory used by postgres for shared memory is the largest of all SHR
columns for postgres columns. Or, about 7.9GB. So, postgres is using
about 7.9GB for shared memory, and very little for anything else.
It's a good idea to check this result agains
Kai Behncke wrote:
>
> But I would like to get it in a php-script, like
>
> $timerequest_result=pg_result($timerequest,0);
>
> (well, that does not work).
>
> I wonder: Is there another way to get the time a request needs?
> How do you handle this?
>
$time = microtime()
$result = pg_result($quer
On 8/17/09 4:43 PM, "Scott Carey" wrote:
>
>
> On 8/17/09 10:24 AM, "Jeremy Carroll"
> wrote:
>
>> I believe this is exactly what is happening. I see that the TOP output lists
>> a
>> large amount ov VIRT & RES size being used, but the kernel does not report
>> this memory as being reserved
On 8/17/09 10:24 AM, "Jeremy Carroll"
wrote:
> I believe this is exactly what is happening. I see that the TOP output lists a
> large amount ov VIRT & RES size being used, but the kernel does not report
> this memory as being reserved and instead lists it as free memory or cached.
Oh! I reca
Hi,
I am using int8 field to pack a number of error flags. This is very common
technique for large tables to pack multiple flags in one integer field.
For most records - the mt_flags field is 0. Here is the statistics (taken from
pgAdmin Statistics tab for mt_flags column):
Most common Values: {
I believe this is exactly what is happening. I see that the TOP output lists a
large amount ov VIRT & RES size being used, but the kernel does not report this
memory as being reserved and instead lists it as free memory or cached.
If this is indeed the case, how does one determine if a PostgreSQ
Dear users,
I try to optimize the time of my Postgresql-requests, but for that, the first
step,
I of course need to get that time.
I know that with:
EXPLAIN ANALYSE SELECT bundesland from
bundesland WHERE ST_Contains(the_geom, $punktgeometrie_start) AND
ST_Contains(the_geom, $punktgeometrie_e
On Sat, 15 Aug 2009, Mark Mielke wrote:
I vote for screwed up reporting over some PostgreSQL-specific explanation. My
understanding of RSS is the same as you suggested earlier - if 50% RAM is
listed as resident, then there should not be 90%+ RAM free. I cannot think of
anything PostgreSQL might
