Re: PostgreSQL MVCC and alternative REDO implementation - my thoughts

2018-11-18 Thread Martín Marqués
El 18/11/18 a las 04:49, Gerhard Wiesinger escribió:
> Hello,
> 
> I just read that blog article and I think switching to REDO logic is not
> a good idea.

I think you got it the other way around. Postgres implementes REDO, that
is, move forward by REDOing the changes which are stored in WAL files

BTW, could you point us to the blog you read this?

Maybe you got REDO and UNDO mixed up.

Saludos,

-- 
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgconf eu 2018 slides entry missing from https://wiki.postgresql.org/wiki/PostgreSQL_Related_Slides_and_Presentations

2018-11-18 Thread Achilleas Mantzios

Hello,

The pgconf eu 2018 entry is missing from 
https://wiki.postgresql.org/wiki/PostgreSQL_Related_Slides_and_Presentations 
.


I am afraid the more time passes since the event the harder to get 
people post their slides there, so pls update this ASAP.





Re: PostgreSQL MVCC and alternative REDO implementation - my thoughts

2018-11-18 Thread Gerhard Wiesinger

On 18.11.2018 12:14, Martín Marqués wrote:

El 18/11/18 a las 04:49, Gerhard Wiesinger escribió:

Hello,

I just read that blog article and I think switching to REDO logic is not
a good idea.

I think you got it the other way around. Postgres implementes REDO, that
is, move forward by REDOing the changes which are stored in WAL files

BTW, could you point us to the blog you read this?

Maybe you got REDO and UNDO mixed up.



Yes, I ment UNDO ...

Link is here:

https://severalnines.com/blog/five-cool-things-i-learned-postgresql-conference-europe-2018

sunday morning, too early :-)

Ciao,

Gerhard





Re: PostgreSQL MVCC and alternative REDO implementation - my thoughts

2018-11-18 Thread Achilleas Mantzios



On 18/11/18 2:04 μ.μ., Gerhard Wiesinger wrote:

On 18.11.2018 12:14, Martín Marqués wrote:

El 18/11/18 a las 04:49, Gerhard Wiesinger escribió:

Hello,

I just read that blog article and I think switching to REDO logic is 
not

a good idea.

I think you got it the other way around. Postgres implementes REDO, that
is, move forward by REDOing the changes which are stored in WAL files

BTW, could you point us to the blog you read this?

Maybe you got REDO and UNDO mixed up.



Yes, I ment UNDO ...

Link is here:

https://severalnines.com/blog/five-cool-things-i-learned-postgresql-conference-europe-2018 



sunday morning, too early :-)



In this blog I had the role of the reporter for the event :)

When and if this makes it to the core, both heaps will be supported. 
Nevertheless this sounds exciting feature to have, however lots of work 
must be done before PostgreSQL is able to adopt this in an elegant manner.





Ciao,

Gerhard







New timeline when starting with a restored data dir

2018-11-18 Thread Yuri Kanivetsky
Hi,

I'm trying to set up Barman, and I've noticed that PostgreSQL 10
creates a new timeline when starting with a restored data dir.
Particularly, when WAL files are delivered via restore_command. When
WAL files are copied to pg_wal dir, no new timeline is created. Is it
to be expected? Can you explain?

I decided to ask here first, since you might know better how
PostgreSQL operates.

Thanks in advance.



Logical replication did not use primary key as replica identity

2018-11-18 Thread Aleš Zelený
Hello,

we are using logical replication for half a year and now, when we were
adding new tables to replication, we have found a unexpected issue in log
file.

New tables were created on publication database (Ubuntu 16.04, PG 10.6) ,
subscription side is PostgreSQL 10.4 (Ubuntu 10.4-2.pgdg16.04+1) on
x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0
20160609, 64-bit.

I've realized, that by a mistake, there were UNIQUE index and primary key
on same set of columns, but dropping unintended unique index and refreshing
subscription did not helped. Also manually defining replica identity did
not resolve the issue. Tables are identical on publisher and subscriber
databases.

postgres=# \c stage_dev
You are now connected to database "stage_dev" as user "postgres".
stage_dev=# \d stage_data.asset_info
Table "stage_data.asset_info"
Column |Type | Collation | Nullable
| Default
---+-+---+--+-
 asset_id  | bytea   |   | not null
|
 call_code | character(3)|   | not null
|
 price_final   | double precision|   |
|
 primary_code_id   | integer |   | not null
|

 updmgr_last_chg_dt| timestamp without time zone |   |
|
Indexes:
"asset_info_pkey" PRIMARY KEY, btree (asset_id, primary_code_id,
call_code)
"asset_info_key" UNIQUE, btree (asset_id, primary_code_id, call_code)
"asset_info_updmgr_idx" btree (updmgr_last_chg_dt) WHERE
updmgr_last_chg_dt IS NOT NULL
Publications:
"pub_stage_dev"

stage_dev=# alter table stage_data.asset_info replica identity using INDEX
asset_info_pkey;
ALTER TABLE
stage_dev=#

Subscription refresh did not helped, neither dropping the mistaken unique
index.

2018-11-18 19:09:31 UTC 22142 5bf1b8df.567e 3 [local] anl_master_dev
postgres 0 14/6766 psql idle [0]:LOG:  statement: alter subscription
sub_stage_dev refresh publication ;

2018-11-18 19:12:22 UTC 23427 5bf1b996.5b83 10 8/40767   [0]:LOG:
logical replication apply worker for subscription "sub_stage_dev" has
started

2018-11-18 19:12:22 UTC 23427 5bf1b996.5b83 20 8/40771
[55000]:ERROR:  logical replication target relation "stage_data.asset_info"
has neither REPLICA IDENTITY index nor PRIMARY KEY and published relation
does not have REPLICA IDENTITY FULL

Any advices, how to find out what I've done wrong and how to resolve the
issue are welcomed. Also I'm interested, why PK is not classified as
suitable replica identity.

Kind regards Ales Zeleny


RE: pgconf eu 2018 slides entry missing from https://wiki.postgresql.org/wiki/PostgreSQL_Related_Slides_and_Presentations

2018-11-18 Thread Charles Clavadetscher
Hello Achilleas

> -Original Message-
> From: Achilleas Mantzios 
> Sent: Sonntag, 18. November 2018 12:23
> To: pgsql-gene...@postgresql.org
> Subject: pgconf eu 2018 slides entry missing from
> https://wiki.postgresql.org/wiki/PostgreSQL_Related_Slides_and_Presentatio
> ns
> 
> Hello,
> 
> The pgconf eu 2018 entry is missing from
> https://wiki.postgresql.org/wiki/PostgreSQL_Related_Slides_and_Presentatio
> ns
> .
> 
> I am afraid the more time passes since the event the harder to get
> people post their slides there, so pls update this ASAP.
> 

[>] I made an entry in the wiki:

https://wiki.postgresql.org/wiki/PostgreSQL_Conference_Europe_Talks_2018

As mentioned there, the slides are linked, as long as they have been delivered 
by the speakers, in the talk descriptions in the schedule.

Bye
Charles





Re: pgconf eu 2018 slides entry missing from https://wiki.postgresql.org/wiki/PostgreSQL_Related_Slides_and_Presentations

2018-11-18 Thread Achilleas Mantzios

On 19/11/18 8:48 π.μ., Charles Clavadetscher wrote:

Hello Achilleas


-Original Message-
From: Achilleas Mantzios 
Sent: Sonntag, 18. November 2018 12:23
To: pgsql-gene...@postgresql.org
Subject: pgconf eu 2018 slides entry missing from
https://wiki.postgresql.org/wiki/PostgreSQL_Related_Slides_and_Presentatio
ns

Hello,

The pgconf eu 2018 entry is missing from
https://wiki.postgresql.org/wiki/PostgreSQL_Related_Slides_and_Presentatio
ns
.

I am afraid the more time passes since the event the harder to get
people post their slides there, so pls update this ASAP.


[>] I made an entry in the wiki:

https://wiki.postgresql.org/wiki/PostgreSQL_Conference_Europe_Talks_2018

As mentioned there, the slides are linked, as long as they have been delivered 
by the speakers, in the talk descriptions in the schedule.


Thank you! Lets hope the list fills up!



Bye
Charles






--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt