| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres pg_cron extension |
| Date: | 2024-02-14 16:08:15 |
| Message-ID: | CANzqJaDxNoRVKEWARdoKFQqOhV6YuG+WpF+6CHihnSNc9iqy9w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Feb 14, 2024 at 10:23 AM Greg Sabino Mullane <htamfids(at)gmail(dot)com>
wrote:
> Yes, definitely the wrong forum. RDS is not Postgres, and "parameter
> groups" is an Amazon thing. A quick web search would seem to indicate that
> the default group is replaced by the custom one, rather than enhancing it.
> But really, this is a simple "try it and see" sort of task.
>
>
> https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/parameter-groups-overview.html
>
Parameter Groups are AWS' name for, and clunky web implementation of,
postgresql.conf. You can use the same Parameter Group for multiple
instances, or you can create a different PaGr for each instance.
(Modifying a PaGr via the aws cli made it tolerably useful.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ayush Vatsa | 2024-02-14 16:28:29 | Query regarding function cleanup in extension upgrade path |
| Previous Message | Greg Sabino Mullane | 2024-02-14 16:00:31 | Re: How should we design our tables and indexes |