Re: Database health check/auditing

Melvin Davidson schrieb am 16.02.2018 um 05:26: > Tim, > > FYI, the policy in this list is to avoid top posting and bottom post instead. Plus: trimming the original content, so that not the whole email thread is repeated in the quote. Thomas

Re: postgres started without auto vaccum

https://bugzilla.redhat.com/show_bug.cgi?id=849428 Virus-free. www.avast.com <

Re: postgres started without auto vaccum

Am 16.02.2018 um 07:23 schrieb Azimuddin Mohammed: Its on rhel 7.3 , i cant disable firewal, its on one of my company dev server. On Feb 16, 2018 12:21 AM, "Andreas Kretschmer" mailto:andr...@a-kretschmer.de>> wrote: On 16 February 2018 06:54:43 CET, Azimuddin Mohammed mailto:azim.

Re: postgres started without auto vaccum

Its on rhel 7.3 , i cant disable firewal, its on one of my company dev server. On Feb 16, 2018 12:21 AM, "Andreas Kretschmer" wrote: > On 16 February 2018 06:54:43 CET, Azimuddin Mohammed > wrote: > >Hello All, > >I am getting below Warning messages in logs after starting postgres, > >can > >so

Re: postgres started without auto vaccum

On 16 February 2018 06:54:43 CET, Azimuddin Mohammed wrote: >Hello All, >I am getting below Warning messages in logs after starting postgres, >can >some please help me here > >LOG: could not bind socket for statistics collector: Cannot assign >requested address > >LOG: disabling statistics collect

postgres started without auto vaccum

Hello All, I am getting below Warning messages in logs after starting postgres, can some please help me here LOG: could not bind socket for statistics collector: Cannot assign requested address LOG: disabling statistics collector for lack of working socket WARNING: autovacuum not started because

Re: postgres not starting

The poster writes " I think the error caused because I removed everything under /data directory before stopping the server. " If you did remove the data directory, you will need to kill any processes hanging on then initdb -D /your/data/directory Without a data directory it will not start.

Re: postgres not starting

Alan Hodgson wrote: > On Thu, 2018-02-15 at 18:21 -0600, Azimuddin Mohammed wrote: > > Hello, > > I am unable to start postgres on one of the server > > I am getting below error "HINT: is another postmaster already running on > > port 5432, if not wait a few seconds and retry" > > I checked the

Re: Database health check/auditing

On Thu, Feb 15, 2018 at 11:03 PM, Tim Cross wrote: > Hi Mel, > > thanks a lot. The databases are all running on Red Hat (well OUL to be > specific). The SQL is fine and I can always wrap them in a bash script if > needed. > > Having these scripts is a real help. My biggest challenge at the moment

Re: Database health check/auditing

Hi Mel, thanks a lot. The databases are all running on Red Hat (well OUL to be specific). The SQL is fine and I can always wrap them in a bash script if needed. Having these scripts is a real help. My biggest challenge at the moment is just turning off my Oracle habits and getting back Postgres o

Re: Database health check/auditing

On Thu, Feb 15, 2018 at 9:22 PM, Tim Cross wrote: > Hi All, > > I was wondering if anyone has some pointers to > sites/repositories/resources for scripts to perform basic database > audits and health checks. > > situation: I have just commenced a DBA and developer role for an > organisation with

Database health check/auditing

Hi All, I was wondering if anyone has some pointers to sites/repositories/resources for scripts to perform basic database audits and health checks. situation: I have just commenced a DBA and developer role for an organisation with a number of Postgres databases (9.4 and 9.6 versions). There has b

Re: postgres not starting

On Thu, 2018-02-15 at 18:21 -0600, Azimuddin Mohammed wrote: > Hello, > I am unable to start postgres on one of the server > I am getting below error "HINT: is another postmaster already running > on port 5432, if not wait a few seconds and retry" > I checked the processes nothing is running with

Re: postgres not starting

Restore a backup or reinstall Postgres. The default Postgres data tables need to be there and owned by the user Postgres runs as. > On Feb 15, 2018, at 5:21 PM, Azimuddin Mohammed wrote: > > Hello, > I am unable to start postgres on one of the server > I am getting below error "HINT: is anot

postgres not starting

Hello, I am unable to start postgres on one of the server I am getting below error "HINT: is another postmaster already running on port 5432, if not wait a few seconds and retry" I checked the processes nothing is running with postgres I think the error caused because I removed everything under /

Re: query's performance

On Thu, 15 Feb 2018 22:43:59 +0100 hmidi slim wrote: > Hi, > I have a table establishment which contains these columns: id, name, > longitude, latitude. > I want to select all the establishments in the table establishment within a > radius from a reference point which is a given establishment. >

Re: Can parallel vacuum commands lead to a lock in Postgres 10.2

On Thu, 15 Feb 2018 17:40:48 +0100 Meikel Bisping wrote: > Hello, > > we have lots of scripts which issue individual vacuum commands to tables > like "vacuum full gxstage_bs" but also general "vaccum full" commands. > Until now these scripts run sequentially and there are no problems. > Now the

query's performance

Hi, I have a table establishment which contains these columns: id, name, longitude, latitude. I want to select all the establishments in the table establishment within a radius from a reference point which is a given establishment. For example: I have a given establishment called establishment1 an

vacuumdb --all Parallel Feature Request

Good afternoon folks. I've been playing around with some vacuumdb options this week as part of post-upgrade testing, in particular with parallel (--jobs=N). I noticed that vacuumdb --all will only work on one database at a time. This means that as it winds down to the last few tables in a particul

Re: Trigger (or something similar) on table rename?

On 02/15/2018 10:52 AM, Ken Tanzer wrote: Hi.  I'm wondering about possibilities for taking action when a table is renamed. I've looked into this a bit. Here is what I understand: Since 9.3 Postgres has had "event triggers" which can run code on DDL events (https://www.postgresql.org/docs/cu

Re: Trigger (or something similar) on table rename?

Ken Tanzer writes: > Something like a trigger on the table rename would be ideal for my > purposes. Anything like that possible? Thanks! Recent PG versions have "event triggers" which would serve the purpose. However, the infrastructure for them isn't very fully built out yet. I'm not sure if y

Re: Trigger (or something similar) on table rename?

On 02/15/2018 10:52 AM, Ken Tanzer wrote: Hi.  I'm wondering about possibilities for taking action when a table is renamed. Specifically in this case, I'm using table_log, which when you use it on a table creates a new table, sequence and index that is tied to the table name.  Of course, if t

Trigger (or something similar) on table rename?

Hi. I'm wondering about possibilities for taking action when a table is renamed. Specifically in this case, I'm using table_log, which when you use it on a table creates a new table, sequence and index that is tied to the table name. Of course, if the oriignal table is renamed, the other relatio

Can parallel vacuum commands lead to a lock in Postgres 10.2

Hello, we have lots of scripts which issue individual vacuum commands to tables like "vacuum full gxstage_bs" but also general "vaccum full" commands. Until now these scripts run sequentially and there are no problems. Now the idea is to run some scripts in parallel, my question is if parallel

RE: Remove default privilege from DB

Hi From: Durumdara [mailto:durumd...@gmail.com] Sent: Donnerstag, 15. Februar 2018 12:41 To: Charles Clavadetscher Cc: Postgres General Subject: Re: Remove default privilege from DB Dear Charles! 2018-02-12 10:03 GMT+01:00 Charles Clavadetscher mailto:clavadetsc...@swisspug.org> >:

Re: Remove default privilege from DB

Dear Charles! 2018-02-12 10:03 GMT+01:00 Charles Clavadetscher : > Hi > > > > *From:* Durumdara [mailto:durumd...@gmail.com] > *Sent:* Montag, 12. Februar 2018 09:32 > *To:* Postgres General > *Subject:* Remove default privilege from DB > > > > Hello! > > > > I need to remove default privileges

Re: Upgrading from Postgresql 9.1 to 10

Thankyou Michael -- Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html

Re: Upgrading from Postgresql 9.1 to 10

On Wed, Feb 14, 2018 at 07:47:55AM -0700, David G. Johnston wrote: > Zero downtime is only possible by standing up a hot-standby then failing > over to it. Same-server upgrade you can do via pg_upgrade but it does > involve downtime. There are lots of material and options online, including > the