agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedFrom: Adrian Klaver <adrian.klaver@aklaver.com>
To: harish Reddy <harishr536@gmail.com>
To: Amitabh Kant <amitabhkant@gmail.com>
Cc: Jayadevan M <maymala.jayadevan@gmail.com>
Cc: pgsql-sql@postgresql.org <pgsql-sql@postgresql.org>
Subject: Re: Fwd: Regarding change in the size of database
Date: Wed, 30 Nov 2016 09:47:26 -0800
Message-ID: <883fefef-6248-a13c-87a5-88ce21dac185@aklaver.com> (raw)
In-Reply-To: <CANiTL_x9p58HcgK917idXONEsJv=XRJMhaKPJz-xHYF-3C=LJg@mail.gmail.com>
References: <CANiTL_y4q--qTBV9A7WnyST2XgqK7RrUa-FV8UrWWY4gwWC4sw@mail.gmail.com>
<CANiTL_zaDiiHzaBscpVXVvjMVMhYmkNyEGPzDf6Vh6VEAvobcQ@mail.gmail.com>
<CANiTL_wu=YwMVkJ5ik4X0OwVSBaZmndpCp18cf2Ubfy7k-8Uxw@mail.gmail.com>
<CAFS1N4iJfQSECDr01Nw-NwO=adfV8qwPDoDtS-Jv6OeKLMEb+A@mail.gmail.com>
<CANiTL_zpTJZJxeNQJ5q3+9eGi03Y1TpbO4HpQrPCpmyySmrwfA@mail.gmail.com>
<CAFS1N4h3d7nKKCYH3mC4-Z-20Q7AuYN+TjhzDQ2BBT5abqAK0w@mail.gmail.com>
<CANiTL_yw14gn5omqUWbu5bqz_ULbNFjtT1+XAC3pQcHhRJXhOQ@mail.gmail.com>
<CAPTAQBKcm55BOx0+pHMQov45YpGFwFLh6ES0h0DNci+mtCBQZQ@mail.gmail.com>
<CANiTL_wjyB6U6ww7spibhUtiNg_jgFCuw5KG3p01Vi1yMj0qqw@mail.gmail.com>
<CAPTAQBJU9eHQVV4wscwNgbskZjLC_0-qO9GjAPHHSj6WhvcGbg@mail.gmail.com>
<CANiTL_xvT6Uud-691vEpggsYQ3OYPC-p_=Nya=j8_9C3+8TbrA@mail.gmail.com>
<CAPTAQBK-paPWU7sa8i0C_THkOwDaY0QSBu-xJWxhT8Ngap71dw@mail.gmail.com>
<CANiTL_x9p58HcgK917idXONEsJv=XRJMhaKPJz-xHYF-3C=LJg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
On 11/30/2016 09:28 AM, harish Reddy wrote:
> I had a doubt regarding this dead tuples does this effect my server
> performance? I have checked at parameter level that auto vacuum is
> turned on. and does auto vacuum cause loss of data?
Not for live data. It makes the space occupied by dead rows available
for use by live rows.
For a full explanation see here:
https://www.postgresql.org/docs/9.6/static/routine-vacuuming.html
>
> On Fri, Nov 11, 2016 at 11:04 AM, Amitabh Kant <amitabhkant@gmail.com
> <mailto:amitabhkant@gmail.com>> wrote:
>
> Rather than looking at connections, you should be looking at the
> average number of active queries you have in your db. That should
> give you a fair idea about the number of connections required.
>
> As for number of connections supported, you will have to give more
> details on the specs of underlying hardware, and if its a dedicated
> db server or sites alongside other services.
>
>
>
> Amitabh
>
> On Fri, Nov 11, 2016 at 10:49 AM, harish Reddy <harishr536@gmail.com
> <mailto:harishr536@gmail.com>> wrote:
>
> Thank you I am analyzing my query statics. So i want to know how
> many connections that postgres database may support and any way
> to archive my database.
>
> On Fri, Nov 4, 2016 at 10:03 AM, Amitabh Kant
> <amitabhkant@gmail.com <mailto:amitabhkant@gmail.com>> wrote:
>
>
>
> On Thu, Nov 3, 2016 at 10:06 AM, harish Reddy
> <harishr536@gmail.com <mailto:harishr536@gmail.com>> wrote:
>
> Hi amitabhkhant sir
> Thank you so much for your answer ,
> I have upgraded my postgres to 9.3 and we are lagging
> lot with performance and could you suggest me the best
> possible parameters to active connections of 200 and
> could you suggest how to install pgbouncer in postgres
> 9.3 and setting up it
>
> Thanks and Regards
> Harish Reddy
>
>
> On Nov 3, 2016 9:20 AM, "Amitabh Kant"
> <amitabhkant@gmail.com <mailto:amitabhkant@gmail.com>>
> wrote:
>
>
>
> On Thu, Oct 27, 2016 at 4:53 PM, harish Reddy
> <harishr536@gmail.com <mailto:harishr536@gmail.com>>
> wrote:
>
>
> Hi Sir,
>
> Thank you for you feedback my postgres is
> running on 9.1 version and when i checked
> that *autovacuum *in* * my production by
> command*ps -axww | grep autovacuum *it says the
> output as it has some process running with this
> id so how to solve my problem but in postgress
> config file it was commented.
>
> My application is an online ERP which is
> supported by *openbravo* has an users of about
> *150(arount 50 active users)* with it and could
> you suggest me the perfect variables to set us
> in postgres config file.
>
> The system has a RAM of 16 GB and the following
> variables
>
> Variable Setting value
> max_connections 200
> shared_buffers 4096MB
> work_mem 24MB
> maintenance_work_mem 512MB
> effective_cache_size 4096MB
>
>
>
>
> On Thu, Oct 27, 2016 at 9:04 AM, Jayadevan M
> <maymala.jayadevan@gmail.com
> <mailto:maymala.jayadevan@gmail.com>> wrote:
>
>
> On Wed, Oct 26, 2016 at 9:51 PM, harish
> Reddy <harishr536@gmail.com
> <mailto:harishr536@gmail.com>> wrote:
>
> Hi Jayadevan,
>
> Firstly Thank you so much for your
> valuable information provided, So what
> should i do for increasing my database
> performance? and could you suggest me
> how to continue to the vacuum process
> and will it decrease my database
> performance?
>
>
> Please read this article
> https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
> <https://wiki.postgresql.org/wiki/Guide_to_reporting_problems;
> i.e - "Mention your database version", "A
> description of what you are trying to
> achieve and what results you expect" etc etc.
> And this.
> https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server
> <https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server;
>
> Do you have autovacuum working?
> https://www.postgresql.org/docs/current/static/runtime-config-autovacuum.html
> <https://www.postgresql.org/docs/current/static/runtime-config-autovacuum.html;
>
>
>
>
> Try installing pgbouncer for connection pooling if
> you need 200 active connections. You can check for
> active connections using answers on this
> page: http://serverfault.com/questions/128284/how-to-see-active-connections-and-current-activity-in-postgr...
> <http://serverfault.com/questions/128284/how-to-see-active-connections-and-current-activity-in-postgr...;
>
> Another suggestion that might come your way is to
> upgrade your postgres version as 9.1 has recently
> been made EOL.
>
> "explain analyze" can be used to debug slow queries.
> See this page for more
> info: https://www.postgresql.org/docs/9.1/static/sql-explain.html
> <https://www.postgresql.org/docs/9.1/static/sql-explain.html;
>
> If you need further help, you will have to be more
> specific on what performance problems you are
> facing, with their explain anaylze output for folks
> here to help you out.
>
> Amitabh
>
>
> There are no "best possible parameters" without knowing what
> is the nature of problem. More specifically, which queries
> are getting slow. Run your queries with "explain analyze
> verbsose" on queries which are getting slow, and then post
> back here to get better answers.
>
> You will also have to give more info about your OS etc for
> folks here to help you out. This was suggested to you
> earlier: https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
> <https://wiki.postgresql.org/wiki/Guide_to_reporting_problems;
>
> For pgbouncer, see this https://pgbouncer.github.io
> <https://pgbouncer.github.io;
>
> Amitabh
>
>
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
view thread (15+ messages)
Message-ID: <883fefef-6248-a13c-87a5-88ce21dac185@aklaver.com>
Permalink: ../883fefef-6248-a13c-87a5-88ce21dac185@aklaver.com/
Also on: postgresql.org/message-id/883fefef-6248-a13c-87a5-88ce21dac185@aklaver.com
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: adrian.klaver@aklaver.com, harishr536@gmail.com, amitabhkant@gmail.com, maymala.jayadevan@gmail.com
Subject: Re: Fwd: Regarding change in the size of database
In-Reply-To: <883fefef-6248-a13c-87a5-88ce21dac185@aklaver.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox