Hello,
I have a question .. okay I know it's a dump but need to ask it because
probably I will need to tell of five of my collective bad things... :)
My version is PostgreSQL 9.6.5 on x86_64-slackware-linux-gnu, compiled
by x86_64-slackware-linux-gcc (GCC) 7.2.0, 64-bit on server IP 10.1.1.3
Tomas, thanks for the heads up!
I certainly didn't know what this setting means, except the obvious name.
Your links helped.
I just can't find where was this setting suggested, but IIRC it was in a
guide for migrating OSM to PostGIS, as other tables were just created by
GDAL OGR.
I had this line
On 23 Červenec 2014, 15:56, klo uo wrote:
> Bill, thanks for your reply.
>
> "shared_buffers" is set to "128MB".
>
> Now that you mention config file, the only thing I did change there, and
> was suggested to me while I made some on my databases was
> "max_locks_per_transaction = 5" (which has
Bill, thanks for your reply.
"shared_buffers" is set to "128MB".
Now that you mention config file, the only thing I did change there, and
was suggested to me while I made some on my databases was
"max_locks_per_transaction = 5" (which has default value 1).
After resetting "max_locks_per_
On Wed, 23 Jul 2014 00:16:47 +0200
klo uo wrote:
>
> Looking in process explorer, I see unusual size for postgres server
> process, i.e. working set reported around 1GB:
> http://i.imgur.com/HmkvFLM.png (same in attachment)
>
> I also use SqlExpress server with several databases (including spat
Hi,
I run Windows and I started using 64 bit PostgreSQL 9.3 a month ago.
I have several PostGIS databases on localhost, with these statistics:
===
Xact
XactRolled Blocks Blocks TuplesTuples
S
On Fri, Jan 10, 2014 at 12:19 PM, Tom Lane wrote:
>
>> Preston Hagar writes:
>> >>> tl;dr: Moved from 8.3 to 9.3 and are now getting out of memory errors
>> >>> despite the server now having 32 GB instead of 4 GB of RAM and the
>> workload
>> >>> and number of clients remaining the same.
>>
>> >
On 10 Leden 2014, 19:19, Tom Lane wrote:
> Preston Hagar writes:
tl;dr: Moved from 8.3 to 9.3 and are now getting out of memory errors
despite the server now having 32 GB instead of 4 GB of RAM and the
workload
and number of clients remaining the same.
>
>> Here are a couple of
Preston Hagar writes:
>>> tl;dr: Moved from 8.3 to 9.3 and are now getting out of memory errors
>>> despite the server now having 32 GB instead of 4 GB of RAM and the workload
>>> and number of clients remaining the same.
> Here are a couple of examples from the incident we had this morning:
> 20
On Fri, Jan 10, 2014 at 11:09 AM, Steve Atkins wrote:
>
> On Jan 10, 2014, at 8:35 AM, Preston Hagar wrote:
>
> > tl;dr: Moved from 8.3 to 9.3 and are now getting out of memory errors
> despite the server now having 32 GB instead of 4 GB of RAM and the workload
> and number of clients remaining
On Jan 10, 2014, at 8:35 AM, Preston Hagar wrote:
> tl;dr: Moved from 8.3 to 9.3 and are now getting out of memory errors despite
> the server now having 32 GB instead of 4 GB of RAM and the workload and
> number of clients remaining the same.
>
>
> Details:
>
> We have been using Postgresq
tl;dr: Moved from 8.3 to 9.3 and are now getting out of memory errors
despite the server now having 32 GB instead of 4 GB of RAM and the workload
and number of clients remaining the same.
Details:
We have been using Postgresql for some time internally with much success.
Recently, we completed a
12 matches
Mail list logo
