Timeline for Best solution for PostgreSQL partial table replication
Current License: CC BY-SA 4.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 29, 2019 at 15:06 | vote | accept | Henry Barker | ||
Mar 28, 2019 at 15:19 | answer | added | Henry Barker | timeline score: 0 | |
Mar 28, 2019 at 11:16 | comment | added | Vérace | Just a thought - I don't know the details of your requirements, but you might want to consider building in a delay period with which you/your client can be happy and your system might be easier to configure and organise under that constaint? | |
Mar 28, 2019 at 7:23 | comment | added | Henry Barker | @Vérace it's still a matter for debate, we haven't decided yet. Got something on your mind? | |
Mar 27, 2019 at 17:03 | comment | added | Vérace | Can you do periodical updates - say every 15 mins? | |
Mar 27, 2019 at 14:54 | answer | added | jjanes | timeline score: 1 | |
Mar 27, 2019 at 14:50 | review | Close votes | |||
Mar 27, 2019 at 17:40 | |||||
Mar 27, 2019 at 14:15 | review | First posts | |||
Mar 27, 2019 at 14:33 | |||||
Mar 27, 2019 at 14:05 | comment | added | user1822 | Ah, OK. Then this wouldn't work. | |
Mar 27, 2019 at 14:04 | comment | added | Henry Barker | @a_horse_with_no_name there is a slow network connection (like 3G) between the sensors and the console | |
Mar 27, 2019 at 14:02 | comment | added | user1822 | Are the servers geographically located wide apart, or is there a fast connection between them. If you upgrade to Postgres 11 (or at least 10), you could create a partitioned table on the master server where each partition is a foreign table to each of the little servers. That way you don't need to replicate anything. | |
Mar 27, 2019 at 13:56 | answer | added | Wellington.carvalho | timeline score: 1 | |
Mar 27, 2019 at 13:47 | history | asked | Henry Barker | CC BY-SA 4.0 |