Pending_restart correctly showed the case where an entry that cannot be changed without a postmaster restart has been modified, but not where the entry had been removed altogether.įix corner-case failure of a new standby to follow a new primary (Dilip Kumar, Robert Haas) pending_restart show as true when the pertinent entry in nf has been removed (Álvaro Herrera)
Now we show replication-protocol commands on the same footing as SQL commands.
Previously, a walsender would show its latest SQL command, which was confusing if it's now doing some replication operation instead. Make walsenders show their latest replication commands in pg_stat_activity (Tom Lane)
#Aws postgresql 10 update
While that's not considered a supported case, the original reason for using a non-transactional update here is long gone, so we may as well change it.Īvoid corrupting the plan cache entry when CREATE DOMAIN or ALTER DOMAIN appears in a cached plan (Tom Lane) This avoids failures when dealing with index predicates that aren't really immutable. Notably, this fixes some cases where it was necessary to be a superuser to use DROP OWNED BY.Īllow index state flags to be updated transactionally (Michael Paquier, Andrey Lepikhov) Skip unnecessary error tests when removing a role from an RLS policy during DROP OWNED BY (Tom Lane) This restriction was not fully checked, which could lead to a PANIC during PREPARE TRANSACTION.įix misbehavior of DROP OWNED BY when the target role is listed more than once in an RLS policy (Tom Lane) This command failed on materialized views containing columns with certain names, notably mv and newdata.įix PREPARE TRANSACTION to check correctly for conflicting session-lifespan and transaction-lifespan locks (Tom Lane)Ī transaction cannot be prepared if it has both session-lifespan and transaction-lifespan locks on the same advisory-lock ID value. The previous coding allowed ALTER EXTENSION ADD/DROP to occur concurrently with DROP EXTENSION, leading to a crash or corrupt catalog entries.įix ALTER SUBSCRIPTION to reject an empty slot name (Japin Li)Īvoid alias conflicts in queries generated for REFRESH MATERIALIZED VIEW CONCURRENTLY (Tom Lane, Bharath Rupireddy)
Make ALTER EXTENSION lock the extension when adding or removing a member object (Tom Lane) Make pg_filenode_relation(0, 0) return NULL rather than failing (Justin Pryzby) In numeric multiplication, round the result rather than failing if it would have more than 16383 digits after the decimal point (Dean Rasheed)įix corner-case errors and loss of precision when raising numeric values to very large powers (Dean Rasheed)įix division-by-zero failure in to_char() with EEEE format and a numeric input value less than 10^(-1001) (Dean Rasheed)įix pg_size_pretty(bigint) to round negative values consistently with the way it rounds positive ones (and consistently with the numeric version) (Dean Rasheed, David Rowley) Reject cases where a query in WITH rewrites to just NOTIFY (Tom Lane) The end result would be a null-pointer dereference in the executor. This should be disallowed, just as FOR UPDATE with a plain GROUP BY is disallowed, but the test for that failed to handle empty grouping sets correctly. GROUP BY GROUPING SETS (()) FOR UPDATE (Tom Lane) Disable the feature altogether on OpenSSL versions that permit doing so, which are 1.1.0h and newer. A maliciously crafted renegotiation request could result in a server crash (see OpenSSL issue CVE-2021-3449). SSL renegotiation has been disabled for some time, but the server would still cooperate with a client-initiated renegotiation request. The source computer and destination computer should have the same operating system.Disallow SSL renegotiation more completely (Michael Paquier) Out-of-place: Restore data to the following destinations:Ĭross-cloud: You can restore PostgreSQL databases from one cloud platform (such as Amazon Web Services and Google Cloud Platform) to a different cloud platform.
In-place: Restore data to the location that it was backed up from The most recent backup: For example, restore the most recent backup to its original locationĪ backup from a specific date: For example, restore data to a point in time before it became unusableīackups from a date range: For example, restore data that was accidentally deleted Restores Backups You Can Use for Restores You can use a file server to back up the following content, which is not included in backups of RDS for PostgreSQL databases: On demand: You can perform on-demand backups at any time On a schedule: The server plan that you assign manages scheduled backups
#Aws postgresql 10 software
You can use the Data Protection Suite software to back up and restore Amazon RDS for PostgreSQL. Software Upgrades, Updates, and Uninstallation >Ĭommvault for Managed Service Providers (MSPs) >
0 kommentar(er)
