| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Techsupport <techsupport(at)sardonyx(dot)in> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: 20220226-Clarification regarding delay time of PostgeSQL starting up |
| Date: | 2022-02-26 19:17:38 |
| Message-ID: | 20220226191738.ghmlckiv2k3xh2kx@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Feb 27, 2022 at 12:04:19AM +0530, Techsupport wrote:
> Hi,
>
> Thanks for your reply.
> Is it a good practice to upgrade / update database on production on every
> year ?
It's a good practice to update all the software you rely on each time a minor
version is released, especially if those contains security fixes. For postgres
new minor version are released at least every 3 months, and sometimes contain
security fixes.
> In my log
> > FATAL: the database system is starting up
> Log showing continuously, other than that there is not PANIC log in the log
> file, which is under the log folder.
There has to be something else in your logs. Your system can't go from normal
processing to "the database system is starting up" without showing any evidence
of some kind of problem. Maybe in the event logs if it's not in your postgres
logs?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mladen Gogala | 2022-02-26 20:58:08 | Re: 20220226-Clarification regarding delay time of PostgeSQL starting up |
| Previous Message | David G. Johnston | 2022-02-26 18:45:31 | Re: 20220226-Clarification regarding delay time of PostgeSQL starting up |