On Monday 10 April 2017 19:37:43 Adrian Klaver wrote:
> On 04/10/2017 01:23 PM, John Iliffe wrote:
> > On Monday 10 April 2017 11:53:35 Daniel Verite wrote:
> >>John Iliffe wrote:
> >>> So, the problem is resolved, although I have no idea why it was
> >>&
Thanks for the idea Rick. It hadn't occurred to me; might have at about
the 200th page :-(
John
=
On Monday 10 April 2017 16:46:14 Rick Widmer wrote:
> On 4/10/2017 2:23 PM, John Iliffe wrote:
> > On Monday 10 April 2017 11:53:35 Danie
On Monday 10 April 2017 11:53:35 Daniel Verite wrote:
> John Iliffe wrote:
> > So, the problem is resolved, although I have no idea why it was
> > necessary.
>
> The key seems to be the PrivateTmp=true in the systemd service.
> Apache is not chrooted as demonst
On Monday 10 April 2017 09:46:54 Daniel Verite wrote:
> John Iliffe wrote:
> > Based on the reference that Joe sent earlier, I do have a second
> > domain socket on /var/pgsql but the problem is how do I get PHP to
> > look there?
>
> pg_connect("host
On Monday 10 April 2017 09:46:54 Daniel Verite wrote:
> John Iliffe wrote:
> > Based on the reference that Joe sent earlier, I do have a second
> > domain socket on /var/pgsql but the problem is how do I get PHP to
> > look there?
>
> pg_connect("host
On Sunday 09 April 2017 23:21:58 Adrian Klaver wrote:
> On 04/09/2017 05:30 PM, John Iliffe wrote:
> > On Sunday 09 April 2017 20:01:32 Adrian Klaver wrote:
> >> So the issue is in PHP via Apache using the socket, because if I
> >> remember right you used localhost in
On Sunday 09 April 2017 22:07:12 rob stone wrote:
> On Sun, 2017-04-09 at 20:09 -0400, John Iliffe wrote:
> > >
> > >
> > > You have Apache, PHP, and Postgres all running on your LAN at
> > > 192.168.1.6.
> > >
> > >
> > >
>
On Sunday 09 April 2017 20:07:01 Adrian Klaver wrote:
> On 04/09/2017 03:27 PM, rob stone wrote:
> > Hello John,
> >
> > Just saw this message.
> >
> >> Still set to the default:
> >>
> >> #listen_addresses = 'localhost' # what IP address(es) to
> >> listen on;
> >>
> >>
On Sunday 09 April 2017 20:01:32 Adrian Klaver wrote:
> On 04/09/2017 02:35 PM, John Iliffe wrote:
> > On Sunday 09 April 2017 17:02:47 Adrian Klaver wrote:
> >> On 04/09/2017 02:00 PM, John Iliffe wrote:
> >>> On Sunday 09 April 2017 15:38:10 Adrian Klaver wrote:
On Sunday 09 April 2017 18:27:49 rob stone wrote:
Hi Rob:
Thanks for chiming in.
> Hello John,
>
> Just saw this message.
>
> > Still set to the default:
> >
> > #listen_addresses = 'localhost' # what IP address(es) to
> > listen on;
> > # comma-
On Sunday 09 April 2017 17:39:30 rob stone wrote:
> Hello John,
>
> > >
> > >
> > > > PHP and Postgresql are both running on same box. It does have
> >
> > two
> >
> > > > interfaces, 192.168.1.6 and 192.168.1.7, and the test programme
> >
> > is
> >
> > > > available on either. The referen
On Sunday 09 April 2017 17:02:47 Adrian Klaver wrote:
> On 04/09/2017 02:00 PM, John Iliffe wrote:
> > On Sunday 09 April 2017 15:38:10 Adrian Klaver wrote:
> >> Remember host != local
> >>
> >> host is for IP connections
> >>
> >> local i
On Sunday 09 April 2017 15:38:10 Adrian Klaver wrote:
> On 04/09/2017 12:37 PM, John Iliffe wrote:
> > On Sunday 09 April 2017 14:34:01 Joe Conway wrote:
> >> On 04/09/2017 11:33 AM, John Iliffe wrote:
> >>> On Saturday 08 April 2017 18:10:35 Joe Conway wrote:
>
On Sunday 09 April 2017 15:41:12 Joe Conway wrote:
> On 04/09/2017 12:37 PM, John Iliffe wrote:
> >> > Thanks Joe. I Changed the pg_connect line in the script to:
> >> > $db_handle = pg_connect('dbname=yrarc host=192.168.1.6 port=5432
> >> >
>
On Sunday 09 April 2017 15:05:18 Adrian Klaver wrote:
> On 04/09/2017 11:33 AM, John Iliffe wrote:
> > On Saturday 08 April 2017 18:10:35 Joe Conway wrote:
> >> On 04/08/2017 01:23 PM, John Iliffe wrote:
> >>> On Saturday 08 April 2017 09:38:07 Adrian Klaver wrote:
&g
On Sunday 09 April 2017 14:34:01 Joe Conway wrote:
> On 04/09/2017 11:33 AM, John Iliffe wrote:
> > On Saturday 08 April 2017 18:10:35 Joe Conway wrote:
> >> On 04/08/2017 01:23 PM, John Iliffe wrote:
> >> > On Saturday 08 April 2017 09:38:07 Adrian Klaver wrote:
>
On Saturday 08 April 2017 11:20:29 Joe Conway wrote:
> On 04/08/2017 06:31 AM, John Iliffe wrote:
> > On Saturday 08 April 2017 00:10:14 Adrian Klaver wrote:
> >> On 04/07/2017 07:45 PM, Joe Conway wrote:
> >> > On 04/07/2017 05:35 PM, Adrian Klaver wrote:
> &
On Saturday 08 April 2017 18:10:35 Joe Conway wrote:
> On 04/08/2017 01:23 PM, John Iliffe wrote:
> > On Saturday 08 April 2017 09:38:07 Adrian Klaver wrote:
> >> So what if you change the connection to use -h localhost?
> >
> > Can you please expand on that request
On Saturday 08 April 2017 09:38:07 Adrian Klaver wrote:
> On 04/08/2017 06:26 AM, John Iliffe wrote:
> > On Saturday 08 April 2017 00:10:14 Adrian Klaver wrote:
> >> On 04/07/2017 07:45 PM, Joe Conway wrote:
> >>> On 04/07/2017 05:35 PM, Adrian Klaver wrote:
>
On Saturday 08 April 2017 09:20:46 Daniel Verite wrote:
> John Iliffe wrote:
> > The proper socket does exist:
> >
> > -
> > ls -al /tmp | grep PGSQL
> > srwxrwxrwx. 1 postgres postgres0 Apr 7 16:53 .s.PGSQL.5432
>
On Saturday 08 April 2017 00:10:14 Adrian Klaver wrote:
> On 04/07/2017 07:45 PM, Joe Conway wrote:
> > On 04/07/2017 05:35 PM, Adrian Klaver wrote:
> >> On 04/07/2017 05:03 PM, John Iliffe wrote:
> >>>>> Running on Fedora 25 with SELinux in PERMISSIVE mode. Th
On Saturday 08 April 2017 00:10:14 Adrian Klaver wrote:
> On 04/07/2017 07:45 PM, Joe Conway wrote:
> > On 04/07/2017 05:35 PM, Adrian Klaver wrote:
> >> On 04/07/2017 05:03 PM, John Iliffe wrote:
> >>>>> Running on Fedora 25 with SELinux in PERMISSIVE mode. Th
On Friday 07 April 2017 22:45:16 Joe Conway wrote:
> On 04/07/2017 05:35 PM, Adrian Klaver wrote:
> > On 04/07/2017 05:03 PM, John Iliffe wrote:
> >>>> Running on Fedora 25 with SELinux in PERMISSIVE mode. The audit
> >>>> log shows no hits on Postgresql.
&g
On Friday 07 April 2017 20:39:55 Adrian Klaver wrote:
> On 04/07/2017 05:10 PM, John Iliffe wrote:
> Actually Ccing list this time
>
> > On Friday 07 April 2017 19:51:57 you wrote:
> >> On 04/07/2017 04:57 PM, John Iliffe wrote:
> >>> Hi Adrian:
> > W
On Friday 07 April 2017 20:35:40 Adrian Klaver wrote:
> On 04/07/2017 05:03 PM, John Iliffe wrote:
>
> Please reply to list also
Yes, sorry about that.
> Ccing list.
>
> > On Friday 07 April 2017 18:58:15 you wrote:
> >> On 04/07/2017 02:38 PM, John Iliffe wrote:
&
===
On Friday 07 April 2017 18:51:33 Adrian Klaver wrote:
> On 04/07/2017 02:38 PM, John Iliffe wrote:
> > When I attempt to run any web application php cannot open a database
> > because of failure to connect. (Please disregard the programme name,
> > it is running in mod_ph
When I attempt to run any web application php cannot open a database
because of failure to connect. (Please disregard the programme name, it is
running in mod_php, not as an fcgi module). The (php) message is:
--
[Fri Apr 07 17:03:28.597101 2017] [php7:warn] [pid 1797:t
On Monday 13 March 2017 19:12:10 Tom Lane wrote:
> John Iliffe writes:
> > Can anybody tell what these files are and what they do, and more
> > importantly if they are needed?
>
> They are database table files, and you will certainly be unhappy if you
> just manually rm
Can anybody tell what these files are and what they do, and more importantly
if they are needed?
This database has been in use since about 2012 on PostgreSQL 9.2 and is
quite active. (both read and insert/change). There seems to be one group
of these files a week, total 316 files as of today
On Friday 10 March 2017 09:25:25 Melvin Davidson wrote:
> On Thu, Mar 9, 2017 at 10:01 PM, John Iliffe wrote:
> > On Thursday 09 March 2017 16:37:28 you wrote:
> > > On 03/08/2017 10:12 AM, John Iliffe wrote:
> > > > I think you may have hit it but I'm even mo
On Thursday 09 March 2017 16:37:28 you wrote:
> On 03/08/2017 10:12 AM, John Iliffe wrote:
> > I think you may have hit it but I'm even more confused now.
> >
> > I looked at the running Postgesql on the current server and there is a
> > 5th sub-directory called /
10:00 AM, Tom Lane wrote:
> > John Iliffe writes:
> > > When the programme exited it left another postmaster.pid file so I
> >
> > deleted
> >
> > > that one too.
> >
> > You haven't shown us the program actually exiting, and basically
On Thursday 09 March 2017 12:49:49 Tom Lane wrote:
> John Iliffe writes:
> > On Thursday 09 March 2017 12:08:01 Tom Lane wrote:
> >> AFAICS, the explanation must be that getaddrinfo() returned two IPv4
> >> addresses, one of which got bound successfully and the other n
On Thursday 09 March 2017 12:08:01 Tom Lane wrote:
> John Iliffe writes:
> > Here is my matching ss output
> >
> > --
> > [root@prod04 John]# ss -l -p | grep post
> > u_str LISTEN 0 128/tmp/.s.PGSQL.5
On Thursday 09 March 2017 09:17:51 Adrian Klaver wrote:
> On 03/08/2017 09:28 PM, Tom Lane wrote:
> > John Iliffe writes:
> >> On Wednesday 08 March 2017 23:35:10 Tom Lane wrote:
> >>> That isn't proving a lot: as I showed in my example lsof output,
>
On Wednesday 08 March 2017 23:35:10 Tom Lane wrote:
> John Iliffe writes:
> > [root@prod04 John]# lsof -n | grep postmaster
> > [root@prod04 John]# lsof -n | grep postgres | grep 5432
> > postgres 2760 postgres5u unix 0x9e5390b5b800
> > 0t0
&
On Wednesday 08 March 2017 17:22:21 Adrian Klaver wrote:
> On 03/08/2017 01:48 PM, John Iliffe wrote:
> > On Wednesday 08 March 2017 15:13:29 Tom Lane wrote:
> >> John Iliffe writes:
> >>> I tried psql but it won't work, as expected, because socket 5432 is
>
On Wednesday 08 March 2017 17:11:16 Adrian Klaver wrote:
> On 03/08/2017 02:01 PM, John Iliffe wrote:
>
> Please use Reply All so others get your posts.
> Ccing list
>
> > On Wednesday 08 March 2017 16:40:03 you wrote:
> >> On 03/08/20
On Wednesday 08 March 2017 15:13:29 Tom Lane wrote:
> John Iliffe writes:
> > I tried psql but it won't work, as expected, because socket 5432 is
> > not available.
>
> Actually, that's not all that expected. psql by default would try to
> connect via a
On Wednesday 08 March 2017 11:18:59 Adrian Klaver wrote:
> On 03/08/2017 07:37 AM, John Iliffe wrote:
> > On Wednesday 08 March 2017 00:01:32 Tom Lane wrote:
> >> John Iliffe writes:
> >>> Now, running as user postgres I try and start as stated in the
On Wednesday 08 March 2017 11:37:27 Adrian Klaver wrote:
> On 03/08/2017 07:37 AM, John Iliffe wrote:
> > On Wednesday 08 March 2017 00:01:32 Tom Lane wrote:
> >> John Iliffe writes:
> >>> Now, running as user postgres I try and start as stated in the
See embedded.
On Wednesday 08 March 2017 00:09:56 Adrian Klaver wrote:
> On 03/07/2017 08:17 PM, John Iliffe wrote:
> > I was unable to get postgres started so I did a very basic
> > compile/install to test it. The configuration line was:
> >
> > ./configure -
On Wednesday 08 March 2017 00:01:32 Tom Lane wrote:
> John Iliffe writes:
> > Now, running as user postgres I try and start as stated in the manual
> > postgres -D /usr/pgsql_tablespaces
> >
> > The result is:
> > [postgres@prod04 postgresql-9.6.2]$ postgres
ready to accept connections
LOG: autovacuum launcher started
When the programme exited it left another postmaster.pid file so I deleted
that one too.
John
===
On Tuesday 07 March 2017 23:26:40 Melvin Davidson wrote:
> On Tue, Mar 7, 2017 at 11:17 PM, John Ili
I was unable to get postgres started so I did a very basic compile/install
to test it. The configuration line was:
./configure --prefix=/usr/postgres-9.6.2
Then I ran make which completed as expected:
make[1]: Leaving directory '/tmp/postgresql-9.6.2/config'
Al
.
Regards, and again, thanks.
John
===
On Tuesday 07 March 2017 16:12:22 Devrim Gündüz wrote:
> Hi,
>
> On Tue, 2017-03-07 at 15:38 -0500, John Iliffe wrote:
> > Trying to compile pgsql 9.6.2 on Fedora 25
> >
> >
Trying to compile pgsql 9.6.2 on Fedora 25
I get the following message:
configure:9345: error: readline library not found
If you have readline already installed, see config.log for details on the
Use --without-readline to disable readline support.
pgac_cv_check_readline=no
libreadline does exis
Thanks to those who replied to my post.
I tried that and works a treat!
Regards.
John
==
On Sat, 2010-16-10 at 17:18 +0100, Raymond O'Donnell wrote:
> On 15/10/2010 22:12, John Iliffe wrote:
> > Does anyone have a way to ru
Does anyone have a way to run pg_dump from cron in a way that doesn't
require someone to enter the password on every run? I get the following
error even when the backup user has read permissions on all application
databases.
The database that fails is part of the PostgreSQL kernel, not my
appli
49 matches
Mail list logo
