Hello,
Getting below error while recovering Postgres
2020-09-11 05:26:54.498 UTC [200369] LOG: database system was shut down at
2020-09-11 05:23:01 UTC
2020-09-11 05:26:54.500 UTC [200369] FATAL: could not access status of
transaction 78961
2020-09-11 05:26:54.500 UTC [200369] DETAIL: Could
Good Day
Firstly I apologise if this has been formally requested before or if there is a
better place for this to go..
While trying to debug why the docker image would not deploy and run on Azure
Kubernetes Service (AKS) I finally got to the bottom of it in that AzureFile
and possible also Azu
On 9/11/20 7:25 AM, Anthony Somerset wrote:
Good Day
Firstly I apologise if this has been formally requested before or if
there is a better place for this to go..
https://www.pgadmin.org/support/issues/
https://azure.microsoft.com/en-us/support/create-ticket/
While trying to debug why the
Hi all,
I got a table with subscriptions to some kind of campaigns, and every contact
can
have max 1 running subscription per campaign:
CREATE TABLE subscriptions
( id SERIAL NOT NULL PRIMARY KEY
, campaign_id INT NOT NULL
, contact_id INT NOT NULL
, done BOOL NOT NULL
);
On Fri, Sep 11, 2020 at 1:31 PM Harmen wrote:
> Hi all,
>
> Are there any known problems with this strategy? Are they any other
> methods of
> inserting lots of records in a nicer way?
>
I do this all the time with insert and it's wonderful. It can get tricky
if you need to do UPDATEs.
You can
