Questions tagged with PostgreSQL
Content language: English
Sort by most recent
I'm newbie to AWS. When I looked at my Bill today, the RDS Backup services were the cause of the rise in the bill.
There isn't a database,nor snapshots or anything operating at the RDS Dashboard, only the standard mysql:80.
How can I terminate the RDS Backup Services?
Hi,
I'm looking to connect the PostgreSQL Database using IAM authentication from Lambda written on Node.js
I see some java script code here but nothing specific for Node.js https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.Connecting.Java.html#UsingWithRDS.IAMDBAuth.Connecting.Java.AuthToken.Connect
I would like to authenticate connection to Aurora PostgreSQL using IAM Authentication.
Any pointer on this is really appreciated.
Postgres database upgrade failed (11.6 -> 13.7) with error:
*pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 6052; 1259 720106 INDEX unq_nickname_ci dba
pg_restore: error: could not execute query: ERROR: function public.unaccent(unknown, text) does not exist
LINE 3: SELECT public.unaccent('public.unaccent', $1) -- schema-qua...
^
HINT: No function matches the given name and argument types. You might need to add explicit type casts.*
After the first failed upgrade, the index and function were deleted, so they don't exist in the catalog, but subsequent upgrades still ends with the same error. Do you have any idea how to proceed?
How do i migrate RDS encrypted cluster to another aws account?
1. Its encrypted DB
2. its a cluster
Based on above,
1. Sharing snapshot wont work
2. copy clustered DB snapshot is not available yet
3. manual export import is not an option
Please suggest ways
Newer versions of Amazon Aurora PostgreSQL-compatible edition are now available and database cluster(s) running Aurora PostgreSQL minor versions 11.13, 11.14, 11.15, 12.8, 12.10, 13.4, 13.5, and 13.6 need to be upgraded by September 15, 2023. These newer minor versions include important updates that will improve the operations of your Aurora PostgreSQL instances and workloads. We strongly encourage you to upgrade to at least a recommended minimum minor version at your earliest convenience.
* For PostgreSQL Minor Version 11.13, 11.14, and 11.15, the recommended minimum minor version is 11.18.
* For PostgreSQL Minor Version 12.8 and 12.10, the recommended minimum minor version is 12.13.
* For PostgreSQL Minor Version 13.4, 13.5 and 13.6, the recommended minimum minor version is 13.9.
Starting on or after 12:00 PM PDT on September 15, 2023, if your Amazon Aurora PostgreSQL cluster has not been upgraded to a newer minor version, we will schedule the relevant recommended minimum minor version to be automatically applied during your next maintenance window. Changes will apply to your cluster during your next maintenance window even if auto minor version upgrade is disabled.
Restoration of Amazon Aurora PostgreSQL 11.13, 11.14, 11.15, 12.8, 12.10, 13.4, 13.5, and 13.6 database snapshots after September 15, 2023 will result in an automatic upgrade of the restored database to a supported version at the time.
How to Determine Which Instances are Running These Minor Versions?
* In the Amazon RDS console, you can see details about a database cluster, including the Aurora PostgreSQL version of instances in the cluster, by choosing Databases from the console's navigation pane.
* To view DB cluster information by using the AWS CLI, use the describe-db-clusters command.
* To view DB cluster information using the Amazon RDS API, use the DescribeDBClusters operation. You can also query a database directly to get the version number by querying the aurora_version() system function i.e., "SELECT * FROM aurora_version();".
How to Apply a New Minor Version
You can apply a new minor version in the AWS Management Console, via the AWS CLI, or via the RDS API. Customers using CloudFormation are advised to apply updates in CloudFormation. We advise you to take a manual snapshot before upgrading. For detailed upgrade procedures, please see the available User Guide [1]. Please be aware that your cluster will experience a short period of downtime when the update is applied.
Visit the Aurora Version Policy [2] and the documentation [3] for more information and detailed release notes about minor versions, including existing supported versions.
If you have any questions or concerns, the AWS Support Team is available on AWS re:Post and via Premium Support [4].
[1] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.html
[2] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.VersionPolicy.html
[3] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Updates.20180305.html
[4] https://aws.amazon.com/support
Hi Team,
I have two RDS Postgres instances in Oregon and Ireland region Both RDS instances are on the engine version 9.6.12. We need to upgrade this version to Postgres engine version 13.3. We tired multiple ways to upgrade the database version upgrading first to minor version 9.6.22 to upgrading to major version 9.6.12. However, when preforming the minor version upgrade, it does not show the list of version available to upgrade in the versions and when trying to upgrade to another minor version, the parameter group for the RDS instance is grayed out. Therefore this is a blocker for us to upgrade the database.
The screenshot of the error is attached. Appreciate your guidance.
Hi,
I need to migrate PostgreSQL DB in AWS.
Is it possible to have an estimate migration's time?
Thanks in advance for your help.
Hi,
I am using AWS Backup to create a snapshot of my Aurora Postgres cluster + instance. In Resource assignments I added arn of cluster and arn of the instance. But backup is only doing a backup of a cluster? So I have one cluster restored but with 0 instances. Why AWS Backup does not backup my RDS instance?
Thanks
[This doc](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/PostgreSQL.Concepts.General.SSL.html#PostgreSQL.Concepts.General.SSL.Requiring) says default value for forcessl is 0 but for postgres 15 default param group it’s 1
This seems like a zeitwerks load issue ... I have manually set the value in ENV same error -
Here is code block of message with trace:
```
`program:~/environment/timpdaley_2 (upgradeRails61to70) $ bin/rails db:migrate RAILS_ENV=development --trace
** Invoke db:migrate (first_time)
** Invoke db:load_config (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:load_config
** Execute db:migrate
== 20230307163758 AddServiceNameToActiveStorageBlobs: migrating ===============
-- table_exists?(:active_storage_blobs)
-> 0.0017s
-- column_exists?(:active_storage_blobs, :service_name)
-> 0.0020s
-- add_column(:active_storage_blobs, :service_name, :string)
-> 0.0014s
rails aborted!
StandardError: An error has occurred, this and all later migrations canceled:
No region was provided. Configure the `:region` option or export the region name to ENV['AWS_REGION']
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-core-3.170.0/lib/aws-sdk-core/plugins/regional_endpoint.rb:92:in `after_initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-core-3.170.0/lib/seahorse/client/base.rb:81:in `block in after_initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-core-3.170.0/lib/seahorse/client/base.rb:80:in `each'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-core-3.170.0/lib/seahorse/client/base.rb:80:in `after_initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-core-3.170.0/lib/seahorse/client/base.rb:24:in `initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-s3-1.119.1/lib/aws-sdk-s3/client.rb:452:in `initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-core-3.170.0/lib/seahorse/client/base.rb:102:in `new'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-s3-1.119.1/lib/aws-sdk-s3/resource.rb:28:in `initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service/s3_service.rb:16:in `new'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service/s3_service.rb:16:in `initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service.rb:61:in `new'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service.rb:61:in `build'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service/configurator.rb:17:in `build'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service/registry.rb:13:in `block in fetch'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service/registry.rb:11:in `fetch'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service/registry.rb:11:in `fetch'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/engine.rb:155:in `block (2 levels) in <class:Engine>'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:95:in `class_eval'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:95:in `block in execute_hook'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:85:in `with_execution_control'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:90:in `execute_hook'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:76:in `block in run_load_hooks'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:75:in `each'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:75:in `run_load_hooks'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/app/models/active_storage/blob.rb:410:in `<top (required)>'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/zeitwerk-2.6.7/lib/zeitwerk/kernel.rb:30:in `require'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/zeitwerk-2.6.7/lib/zeitwerk/kernel.rb:30:in `require'
/home/ubuntu/environment/timpdaley_2/db/migrate/20230307163758_add_service_name_to_active_storage_blobs.active_storage.rb:9:in `up'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:873:in `public_send'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:873:in `exec_migration'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:854:in `block (2 levels) in migrate'
/home/ubuntu/.rvm/rubies/ruby-3.0.0/lib/ruby/3.0.0/benchmark.rb:293:in `measure'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:853:in `block in migrate'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:215:in `with_connection'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:852:in `migrate'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1046:in `migrate'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1360:in `block in execute_migration_in_transaction'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/connection_adapters/abstract/transaction.rb:319:in `block in within_new_transaction'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/connection_adapters/abstract/transaction.rb:317:in `within_new_transaction'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/connection_adapters/abstract/database_statements.rb:316:in `transaction'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/transactions.rb:209:in `transaction'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1411:in `ddl_transaction'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1359:in `execute_migration_in_transaction'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1333:in `each'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1333:in `migrate_without_lock'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1282:in `block in migrate'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1432:in `block in with_advisory_lock'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:215:in `with_connection'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1447:in `with_advisory_lock_connection'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1428:in `with_advisory_lock'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1282:in `migrate'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1117:in `up'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:1092:in `migrate'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/tasks/database_tasks.rb:262:in `migrate'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/railties/databases.rake:92:in `block (2 levels) in <top (required)>'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/task.rb:281:in `block in execute'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/task.rb:281:in `each'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/task.rb:281:in `execute'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/task.rb:199:in `synchronize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/task.rb:199:in `invoke_with_call_chain'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/task.rb:188:in `invoke'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/application.rb:160:in `invoke_task'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/application.rb:116:in `block (2 levels) in top_level'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/application.rb:116:in `each'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/application.rb:116:in `block in top_level'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/application.rb:125:in `run_with_threads'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/application.rb:110:in `top_level'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/railties-7.0.4.2/lib/rails/commands/rake/rake_command.rb:24:in `block (2 levels) in perform'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/application.rb:186:in `standard_exception_handling'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/railties-7.0.4.2/lib/rails/commands/rake/rake_command.rb:24:in `block in perform'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/rake-13.0.6/lib/rake/rake_module.rb:59:in `with_application'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/railties-7.0.4.2/lib/rails/commands/rake/rake_command.rb:18:in `perform'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/railties-7.0.4.2/lib/rails/command.rb:51:in `invoke'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/railties-7.0.4.2/lib/rails/commands.rb:18:in `<top (required)>'
bin/rails:4:in `require'
bin/rails:4:in `<main>'
Caused by:
Aws::Errors::MissingRegionError: No region was provided. Configure the `:region` option or export the region name to ENV['AWS_REGION']
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-core-3.170.0/lib/aws-sdk-core/plugins/regional_endpoint.rb:92:in `after_initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-core-3.170.0/lib/seahorse/client/base.rb:81:in `block in after_initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-core-3.170.0/lib/seahorse/client/base.rb:80:in `each'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-core-3.170.0/lib/seahorse/client/base.rb:80:in `after_initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-core-3.170.0/lib/seahorse/client/base.rb:24:in `initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-s3-1.119.1/lib/aws-sdk-s3/client.rb:452:in `initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-core-3.170.0/lib/seahorse/client/base.rb:102:in `new'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/aws-sdk-s3-1.119.1/lib/aws-sdk-s3/resource.rb:28:in `initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service/s3_service.rb:16:in `new'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service/s3_service.rb:16:in `initialize'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service.rb:61:in `new'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service.rb:61:in `build'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service/configurator.rb:17:in `build'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service/registry.rb:13:in `block in fetch'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service/registry.rb:11:in `fetch'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/service/registry.rb:11:in `fetch'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/lib/active_storage/engine.rb:155:in `block (2 levels) in <class:Engine>'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:95:in `class_eval'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:95:in `block in execute_hook'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:85:in `with_execution_control'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:90:in `execute_hook'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:76:in `block in run_load_hooks'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:75:in `each'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activesupport-7.0.4.2/lib/active_support/lazy_load_hooks.rb:75:in `run_load_hooks'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activestorage-7.0.4.2/app/models/active_storage/blob.rb:410:in `<top (required)>'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/zeitwerk-2.6.7/lib/zeitwerk/kernel.rb:30:in `require'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/zeitwerk-2.6.7/lib/zeitwerk/kernel.rb:30:in `require'
/home/ubuntu/environment/timpdaley_2/db/migrate/20230307163758_add_service_name_to_active_storage_blobs.active_storage.rb:9:in `up'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:873:in `public_send'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/active_record/migration.rb:873:in `exec_migration'
/home/ubuntu/.rvm/gems/ruby-3.0.0@timdaley_2/gems/activerecord-7.0.4.2/lib/
```
Querying from redshift to serverless aurora in cross account facing error as Timeout Expired,Debug Driver logs from
com.amazon.redshift.core.v3.QueryExecutorImpl.receiveErrorResponse: <=BE ErrorMessage(ERROR: timeout expired
Location: File: ../src/external_catalog/external_catalog_api.cpp, Routine: localize_external_table, Line: 1267
Server SQLState: D;600)
Cross account set up well verified:Anoynomus details below
nc -vz auroradnsname.rds.amazonaws.com 5432
Connection to auroradnsname.rds.amazonaws.com 5432 port [tcp/postgres] succeeded!
P.S :Instead of VPC peering using aws transit gateway
I've been leveraging the pg_cron extension to run scheduled precompute jobs within the Postgres DB for over a year now, and have never had this issue.
This extension comes with a table that logs the jobs that need to be run, as well as a function that allows you to easily create new jobs and insert them into the table. Today, when trying to schedule a new cron job in the Postgres DB, the DB crashed - terminating all existing connection to the DB.
We haven't changed anything in the DB since yesterday, so it is confusing as to why this extension may be related to the crash. I'm hoping someone can help provide some insight.