On Sun, May 13, 2018 at 01:39:48AM +0200, Hannes Erven wrote:
> what is Postgresql's strategy when to fetch WAL from the master while in
> streaming replication, and could it be tweaked?
>
> I'm using a physical streaming replication slave to have a database lagging
> behind about one month behind
Hi,
what is Postgresql's strategy when to fetch WAL from the master while in
streaming replication, and could it be tweaked?
I'm using a physical streaming replication slave to have a database
lagging behind about one month behind the primary, by setting
"recovery_target_time" to the desire
On 05/12/2018 10:22 AM, Francisco Olarte wrote:
Adrian:
On Sat, May 12, 2018 at 6:42 PM, Adrian Klaver
wrote:
On 05/12/2018 04:04 AM, Francisco Olarte wrote:
...
Can you post an example ( correct, error inputs, preferrably done with
psql ) ?
At this point I do not know if it is working or
Adrian:
On Sat, May 12, 2018 at 6:42 PM, Adrian Klaver
wrote:
> On 05/12/2018 04:04 AM, Francisco Olarte wrote:
...
>> Can you post an example ( correct, error inputs, preferrably done with
>> psql ) ?
>>
>> At this point I do not know if it is working or if it seems to working
>> for you. I see
On 05/12/2018 04:04 AM, Francisco Olarte wrote:
On Thu, May 10, 2018 at 10:37 PM, Ben Hood wrote:
On 10 May 2018, at 16:33, Francisco Olarte wrote:
For what you want to do I think you'll have to parse the text value,
maybe by definig a view with a text columns and using some
rule/trigger magi
On 05/11/2018 03:54 PM, hmidi slim wrote:
Hi,
I want to get some different opinions and tips about two different
conception.
I want to create a table named proudct_price_period
createtableproduct_price_period {
id integer,
product_id integer,
occupation_type_id integer,
price_mode_id integer,
p
On Thu, May 10, 2018 at 10:37 PM, Ben Hood wrote:
> On 10 May 2018, at 16:33, Francisco Olarte wrote:
>
> For what you want to do I think you'll have to parse the text value,
> maybe by definig a view with a text columns and using some
> rule/trigger magic for insert / updates.
>
>
> Sorry for be
