PDXPUG – January meeting

When: 6-8pm Thursday Jan 19, 2017
Where: iovation
Who: Mark Wong
What: pglogical

Mark Wong will give an overview of pglogical, the latest replication option for Postgres. It’s a lower-impact option than trigger-based replication, and features include the ability to replicate only the databases and tables you choose from a cluster. Part of the talk will cover use cases and future development plans.

Find out more here: https://2ndquadrant.com/en/resources/pglogical/

Mark leads the 2ndQuadrant performance practice as a Performance Consultant for English Speaking Territories, based out of Oregon in the
USA.


If you have a job posting or event you would like me to announce at the meeting, please send it along. The deadline for inclusion is 5pm the day before the meeting.

Our meeting will be held at iovation, on the 32nd floor of the US Bancorp Tower at 111 SW 5th (5th & Oak). It’s right on the Green & Yellow Max lines. Underground bike parking is available in the parking garage; outdoors all around the block in the usual spots. No bikes in the office, sorry!

iovation provides us a light dinner (usually sandwiches or pizza).

Elevators open at 5:45 and building security closes access to the floor at 6:30.

See you there!

Advertisements

PDXPUG: February meeting in two weeks

When: 6-8pm Thu Feb 19, 2015
Where: Iovation
Who: David Kerr
What: Using Bucardo to Migrate your Pg database to RDS with minimal downtime

As a followup to January’s RDS discussion, Dave Kerr works through strategies to move your existing Postgres database into RDS.

Using Bucardo and Master/Master Replication we can achieve a migration to RDS with minimal or no downtime.

Dave will show some tools and techniques so help facilitate this transition as well as go over the idiosyncrasies of using Bucardo with RDS.

Our meeting will be held at Iovation, on the 32nd floor of the US Bancorp Tower at 111 SW 5th (5th & Oak). It’s right on the Green & Yellow Max lines. Underground bike parking is available in the parking garage; outdoors all around the block in the usual spots. No bikes in the office, sorry!

Elevators open at 5:45 and building security closes access to the floor at 6:30.

The building is on the Green & Yellow Max lines. Underground bike parking is available in the parking garage; outdoors all around the block in the usual spots.

See you there!

PDXPUG Lab – Streaming Rep Saturday Part 3 happens in two weeks.

When: Thu May 8, 6pm-9pm (dinner provided)
Where: Emma, B-side 6 Building, 5th floor

Yeah, we’re not quite finished yet. But I expect that this will be the last one & we’ll move on to something else next time.

The general plan:
– review of setup
– try this: https://github.com/darkixion/pg_rep_test
– look into the monitoring
– alternatives to the ‘cp’ archiving command example
– failover & recovery

As before, you are welcome to come to this one, even if you missed the first two.

Please come prepared with a laptop with two Postgres clusters of the same version installed. You can do this by having a couple of VMs, linux containers, or just run two instances of Pg on different ports. If you don’t understand how to do that, or you don’t have a laptop of your own, please let me know when you sign up, and we’ll take care of that for you.

Space is limited, so please sign up in advance.

Dinner provided by PDXPUG.
Space provided by Emma.

Streaming Rep Lab Part 2 – recap

We had our Streaming Rep Lab followup last night1. It was mostly successful: half of the new people got it up & running, and the people who’d been at the previous workshop got to experiment with almost everything on the agenda.

The cheatsheet is up on our git repo: https://github.com/pdxpug/cheatsheets 2.

We talked a bit about monitoring and messed around with some of the available functions (e.g. pg_last_xact_replay_timestamp), started looking at pg_xlogdump (for “educational purposes”, of course), checked out a packet capture between the master & standby, and finished up with breaking the link between the master & the standby: the standby cried a bit about not being able to reach the master, but as soon as we restored the link, everything was fine.

The overarching theme of the evening is that we need to come up with a more robust plot to make Postgres fail in an interesting way.

SELECT pg_last_xact_replay_timestamp(); will give you a WAL ID, but is only valid on a standby.
The function to translate it to a file name: SELECT pg_xlogfile_name([id]); can only be run on the master. So that’s kinda weird and requires some puzzling out.

I started a wiki page of ideas for future labs, but we may be hung up on streaming rep & breaking it for a little while πŸ™‚

Thanks to Emma for hosting & providing dinner!



1 – With a puppy.
2 – Yes, I know there is something wrong with the step numbering. It renders correctly in github’s md validator, but not when I upload it.

Streaming Rep Lab, Part 2 – two weeks from today

When: Thu Feb 27, 6pm-9pm (light dinner provided)
Where: Emma, B-side 6 Building, 5th floor

This is in addition to our regular monthly meeting, which is next week.

We didn’t quite get everything covered last time, so we’re having a followup lab to:
– practice recovery (which means we’ll be breaking it πŸ™‚ )
– discuss monitoring options
– check out the human-readable WAL

You are welcome to attend if you couldn’t make the first lab. We’ll have a quick review of what we did, but won’t be spending too much time on it. As with the previous lab, there is no set schedule or exercises – we’ll make it up as we go.

Please come prepared with a laptop with the SR setup of your choice. Bonus points if it’s broken and we need to troubleshoot it. (SR, not your hardware.)

Space is limited, so please sign up in advance:

[PDXPUG] Streaming Rep Saturday Recap

6 folks turned out for our first Streaming Replication lab day. Here’s what we accomplished:

– lively discussion about the different pieces involved (WAL files, various GUCs, etc)
– worked on a step-by-step cheatsheet
– got sr running between two vms, between two Pg instances on the same VM on different ports, and between two Pg instances on the same VM via unix sockets
– learned some new tools (terminator, anyone?)
– spread the \e love

There will be a followup to this lab, as we didn’t cover everything we wanted to, and (of course) created more questions for ourselves.

Thanks to everyone who attended for taking time to hang out inside on a sunny day, and to EDB and Emma for lunch and facilities!

Our next regular meeting will be Thursday Feb 20th; watch for the announcement next week.

Streaming Rep Saturday

We’re having a lab day!

When: Sat Jan 25, 10am-2pm (lunch provided)
Where: Emma, B-side 6 Building, 5th floor

Come experiment with streaming rep in a friendly environment with a delicious lunch and beverages, instead of in a crisis environment with your boss breathing down your neck.

Agenda, as much as we ever have one:
– Discussion of the various configurations (streaming rep, hot standby, etc)
– Actual setup
– Is it working?
– Discussion of results
– If time allows, we’ll come up with creative ways to break it and look at what’s required to recover.

As for previous labs, we have limited space. Please sign up here.

Please come prepared with a laptop with two VMs, both with the latest version of Postgres installed. If you don’t have a laptop, we can set up VMs for you on the community equipment – please indicate that when you sign up, because we need some lead time to do that.

If you have any tips, tricks, questions, or horror stories, please bring those, too!

Lunch provided by EnterpriseDB.
Space provided by Emma.