On 04/07/2017 08:56 PM, rob stone wrote:
Hello Adrian,
On Thu, 2017-04-06 at 21:24 -0700, Adrian Klaver wrote:
On 04/06/2017 08:01 PM, rob stone wrote:
That is the default location and is generally the case in a source
install. Package maintainers can and do often put them elsewhere.
rob stone wrote:
> You create a new cluster by running initdb:-
>
> initdb -D /path/to/my/new/cluster
No, if you want to use the infrastructure brought by the
debian packages for your cluster, it should be created with:
pg_createcluster 9.5 nameofcluster
See
Hello Adrian,
On Thu, 2017-04-06 at 21:24 -0700, Adrian Klaver wrote:
> On 04/06/2017 08:01 PM, rob stone wrote:
> >
> >
> >
> That is the default location and is generally the case in a source
> install. Package maintainers can and do often put them elsewhere.
> AFAIK
> the Debian/Ubuntu
On 04/05/2017 09:05 PM, Tom Lane wrote:
(But ... these statements are based on an assumption of out-of-the-
box Postgres behavior. I would not exactly put it past the Debian
packagers to have decided to change this for reasons of their own,
and their track record of telling us about such
Re: Magnus Hagander 2017-04-06
> On Thu, Apr 6, 2017 at 3:46 PM, Stephen Frost wrote:
>
> > * Tom Lane (t...@sss.pgh.pa.us) wrote:
> > > (But ... these statements are based on an assumption of out-of-the-
>
On 04/06/2017 08:01 PM, rob stone wrote:
On Thu, 2017-04-06 at 15:58 -0700, Adrian Klaver wrote:
On 04/06/2017 03:16 PM, rob stone wrote:
Which is what has me confused. If you are using the postgresql-
common
system then the *.conf files should be in
On Thu, 2017-04-06 at 15:58 -0700, Adrian Klaver wrote:
> On 04/06/2017 03:16 PM, rob stone wrote:
> >
> >
>
> Which is what has me confused. If you are using the postgresql-
> common
> system then the *.conf files should be in
> /etc/postgresql/version/cluster_name/.
>
> Where exactly is
On 04/06/2017 03:16 PM, rob stone wrote:
On Wed, 2017-04-05 at 21:14 -0700, Adrian Klaver wrote:
What repos are you using, the Debian or the PGDG one?
I guess the question I should really ask is, are you using a repo or
some other method to upgrade?
Upgraded from standard Debian repos.
On Wed, 2017-04-05 at 21:14 -0700, Adrian Klaver wrote:
>
> What repos are you using, the Debian or the PGDG one?
>
> I guess the question I should really ask is, are you using a repo or
> some other method to upgrade?
>
>
Upgraded from standard Debian repos.
Nothing else was changed
On Thu, Apr 6, 2017 at 3:46 PM, Stephen Frost wrote:
> Tom,
>
> * Tom Lane (t...@sss.pgh.pa.us) wrote:
> > (But ... these statements are based on an assumption of out-of-the-
> > box Postgres behavior. I would not exactly put it past the Debian
> > packagers to have decided
Tom,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> (But ... these statements are based on an assumption of out-of-the-
> box Postgres behavior. I would not exactly put it past the Debian
> packagers to have decided to change this for reasons of their own,
> and their track record of telling us about
On Thu, Apr 06, 2017 at 12:05:51AM -0400, Tom Lane wrote:
> rob stone writes:
> > Upgraded to version 9.6.2-2 and these are the log entries on start-up:-
>
> > 2017-04-05 08:03:29 AESTLOG: test message did not get through on
> > socket for statistics collector
...
>
On 04/05/2017 08:03 PM, rob stone wrote:
Hello,
Postgres is started via pg_ctl and NOT systemd.
Below are the log entries when version 9.6.2-1 is started.
2017-04-04 07:15:27 AESTLOG: database system was shut down at 2017-04-
03 13:08:27 AEST
2017-04-04 07:15:28 AESTLOG: MultiXact member
rob stone writes:
> Upgraded to version 9.6.2-2 and these are the log entries on start-up:-
> 2017-04-05 08:03:29 AESTLOG: test message did not get through on
> socket for statistics collector
This is not something that would be affected by any Postgres setting;
the stats
Hello,
Postgres is started via pg_ctl and NOT systemd.
Below are the log entries when version 9.6.2-1 is started.
2017-04-04 07:15:27 AESTLOG: database system was shut down at 2017-04-
03 13:08:27 AEST
2017-04-04 07:15:28 AESTLOG: MultiXact member wraparound protections
are now enabled
15 matches
Mail list logo