References: 
 <CALQkqm_BqAU9Nh=morY6ON02fGjZ228YfAEkBeqZwA5QPjh5wg@mail.gmail.com>
	<8b8abf0c137c0dac2d29c163537a7ea2@imap.lan.net>
 <CALQkqm-69GZtNU+sxehM7PAYS1SPjjN_N3=b2diG4UFTA3zHWA@mail.gmail.com>
Message-ID: <1403268386.87807.YahooMailNeo@web122301.mail.ne1.yahoo.com>
Date: Fri, 20 Jun 2014 05:46:26 -0700
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
Subject: Re: Postgresql not getting assigned memory
To: Oliver <ofabelo@gmail.com>, Jan Lentfer <Jan.Lentfer@web.de>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
In-Reply-To: 
 <CALQkqm-69GZtNU+sxehM7PAYS1SPjjN_N3=b2diG4UFTA3zHWA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Oliver <ofabelo@gmail.com> wrote:

> $ more PG_VERSION
> 9.3

If you can start the databased service and connect to it, the best
way to check the version is:

=A0 SELECT version();

If you can't start the service, you can do this:

=A0 $ postgres --version

(You may need to specify the path to the postgres executable.)

Either way you should be able to determine the minor release.=A0 It
is always a good idea to keep up-to-date on minor releases (where
the version number only changes to the right of the second dot),
because in PostgreSQL we only include fixes for serious bugs and
security vulnerabilities in minor releases, not new features.=A0 See
this page for additional discussion of the issue:

http://www.postgresql.org/support/versioning/

This is even more important than usual for 9.3, which had some data
corruption bugs in early versions.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin