‐‐‐ Original Message ‐‐‐
On Tuesday, January 29, 2019 9:20 PM, Tim Cross wrote:
> On Wed, 30 Jan 2019 at 07:49, Jason W wrote:
>
>> I have two postgresql accounts created by someone else who I do not know (So
>> I do not know setting for those accounts and tables created). One is read
I have a complex query which puts my server in recovery mode every time I run
it. I don´t need to say that recovery mode is a situation you don´t want
your server goes to.*If I´m using some subselects I´ll get that
situation*with StatusTrabalhando(Intkey) as (select Intkey from sys_Lookup
where Gr
I´m using Postgres 10 on ubuntu in a Google VM (8 cores, 32Gb RAM, 250Gb SSD)
and DB has 70GB
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
On 2/3/19 7:53 AM, PegoraroF10 wrote:
First the below is unreadable, probably because it is being sent through
Nabble. Please subscribe to list directly and try again. In meantime
could not tell from below, but what relevant information is in the logs
before and after?
I have a complex query
Just to be readable ...
And ... server log has only "the database system is in recovery mode" every
time I run that query.
I have a complex query which puts my server in recovery mode every time I
run it.
I don´t need to say that recovery mode is a situation you don´t want your
server goes to.
On 2/3/19 8:32 AM, PegoraroF10 wrote:
Just to be readable ...
And ... server log has only "the database system is in recovery mode" every
time I run that query.
I would assume that is in the log from the restart of the server after
it crashed and then restarted in recovery mode.
What is in
On Sun, Feb 03, 2019 at 10:05:46AM -0800, Adrian Klaver wrote:
> On 2/3/19 8:32 AM, PegoraroF10 wrote:
>> I have a complex query which puts my server in recovery mode every time I
>> run it.
>> I don´t need to say that recovery mode is a situation you don´t want your
>> server goes to.
Do you mean
I have a database which stores receiver to indicate which account the data
relates to. This has led to tons of duplication of data, as one set of data may
create 3 separate rows, where the only difference is the receiver column.
|-|--|-|---
Olá Marcos,
> My original query, which worked for some days and then went to
> recovery mode
> was ...
If it was working and then ceased to function, did any of the following
occur:-
1) Postgres version changed?
2) OS version changed?
3) Schema changes affecting the tables/views used in your q
Hi,
with pg v10.1
I have a setup enabled as below.
7 shards ( 1RW, 2 RO )
they all are fronted by FDW talking to each other.
we use writes directly to shards, and reads via FDW from all shards (RO)
our DB size is ~ 500GB each shard, and tables are huge too.
1 table ~ 200GB, 1 ~55GB, 1 ~40GB and
10 matches
Mail list logo
