On Wed, April 1, 2015 9:25 am, FarjadFarid(ChkNet) [via PostgreSQL] wrote: >
> > It sounds like your system had crashed several times. > > > My suggestion would be first ensure that your tables and indexes are not > corrupted. > > Second suggestion is to ensure your index is tightly represents the data > you are accessing. The tighter it is the faster the response time. The > less memory and CPU usage. > > Of course these are basic for any good DB but these essential before > moving to more complex issues. > > > > -----Original Message----- > From: pgsql-general-ow...@postgresql.org > [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Bill Moran > Sent: 01 April 2015 13:48 > To: TonyS > Cc: pgsql-general@postgresql.org > Subject: Re: [GENERAL] Would like to know how analyze works technically > > > On Wed, 1 Apr 2015 04:33:07 -0700 (MST) > TonyS <t...@exquisiteimages.com> wrote: > > >> On Wed, April 1, 2015 12:18 am, Tom Lane-2 [via PostgreSQL] wrote: >> >>> >>> TonyS <t...@exquisiteimages.com> writes: >>> >>> >>>> Running "analyze verbose;" and watching top, the system starts out >>>> using no swap data and about 4GB of cached memory and about 1GB of >>>> used memory. As it runs, the amount of used RAM climbs, and >>>> eventually the used swap memory increases to 100% and after being at >>>> that level for a couple of minutes, the analyze function crashes and >>>> indicates "server closed the connection unexpectedly." >>> Thanks for the suggestion. What command/tool do you use to check a PostgreSQL database for corruption? -- View this message in context: http://postgresql.nabble.com/Would-like-to-know-how-analyze-works-technically-tp5844197p5844259.html Sent from the PostgreSQL - general mailing list archive at Nabble.com.
