Ah, this is why I scroll through my threads view repeatedly...
Well, putting fires out is one thing, but that's not everything.
It sounds like you've basically dug a hole inside Oracle and lived in it for 10 years. That certainly works, but as you've found, can be very insular. So, spinning up a different database, or even databases plural, so you can learn difference between Oracle and what else is out there, would generally be a good idea.
Understanding how to set up a new database installation and tune it would also be good. If the above point refers to having a broad understanding of different systems, this point covers having some level of depth with each system, particularly configuration. (The thing that popped into my head was the possibility that... maybe... one day you'd get the opportunity to go "actually, I know of a faster way to solve this database problem - if we use this free database over here types for 4 seconds and suddenly a new PG installation is running we can just import the data types for 2 more seconds and the data is imported and then writes query on first try in 8 seconds get the result we need." "...Can you move this off your laptop?" "Sure! :D"
Okay, I have no idea if the above would ever happen where you currently are :) but it's of course a good idea to be confident with configuration, setup, optimization, how things can fall apart and explode, etc.
One idea: when confronted with a real-world issue, if you're in an environment that will let you clip out bits of production data and play with them on your own machine for testing, it might be useful/interesting to figure out how to solve a given problem on multiple databases. (Translation: if you follow the path you're on, it's possible you'll be using something other than Oracle. You could use your current prod data as homework on "but how do I do X for Y DB?", and save the boredom of using synthetic lorem ipsum. You might find certain databases work faster for certain queries than Oracle does, which wouldn't surprise me at all.)
Also, on https://www.postgresql.org/community/, I found the link to the https://www.postgresql.org/list/pgsql-jobs/ mailinglist; this is basically a "Who is hiring?" specifically for PG-related stuff. This immediately makes me wonder: what should someone who's stared at Oracle for 10 years focus on with PG, so they could competently pick something up from here and run with it? (Might be a question for IRC, Slack or the mailinglists.)
Thanks very much for mentioning that you are in Russia in a previous comment :) this gave me more bits of entropy to throw at Google and found some potentially interesting results.
So... this brought up a new idea that could be very interesting: you could specialize in Oracle-to-PostgreSQL migrations! This may well be a very worthwhile investment of time; large installations that need Everything And Especially All The Details® to Just Work And Simply Never Ever Fall Over™ are naturally going to be more than happy throwing you piles of money. I imagine that even in an assistant or entry-level position (being pragmatic; no insult intended) the associated portions allocated to you from said piles of money may still be appreciable. (Something I think about a lot is "where does everything scale so much it leaks tons of money?" :D)
Well, putting fires out is one thing, but that's not everything.
It sounds like you've basically dug a hole inside Oracle and lived in it for 10 years. That certainly works, but as you've found, can be very insular. So, spinning up a different database, or even databases plural, so you can learn difference between Oracle and what else is out there, would generally be a good idea.
Understanding how to set up a new database installation and tune it would also be good. If the above point refers to having a broad understanding of different systems, this point covers having some level of depth with each system, particularly configuration. (The thing that popped into my head was the possibility that... maybe... one day you'd get the opportunity to go "actually, I know of a faster way to solve this database problem - if we use this free database over here types for 4 seconds and suddenly a new PG installation is running we can just import the data types for 2 more seconds and the data is imported and then writes query on first try in 8 seconds get the result we need." "...Can you move this off your laptop?" "Sure! :D"
Okay, I have no idea if the above would ever happen where you currently are :) but it's of course a good idea to be confident with configuration, setup, optimization, how things can fall apart and explode, etc.
One idea: when confronted with a real-world issue, if you're in an environment that will let you clip out bits of production data and play with them on your own machine for testing, it might be useful/interesting to figure out how to solve a given problem on multiple databases. (Translation: if you follow the path you're on, it's possible you'll be using something other than Oracle. You could use your current prod data as homework on "but how do I do X for Y DB?", and save the boredom of using synthetic lorem ipsum. You might find certain databases work faster for certain queries than Oracle does, which wouldn't surprise me at all.)
To get at the question you asked - figuring out how to get started - this is very context-specific and not something I can effectively answer; IRC could be a good starting point: I found https://www.postgresql.org/community/irc/, and also https://postgres-slack.herokuapp.com/.
Also, on https://www.postgresql.org/community/, I found the link to the https://www.postgresql.org/list/pgsql-jobs/ mailinglist; this is basically a "Who is hiring?" specifically for PG-related stuff. This immediately makes me wonder: what should someone who's stared at Oracle for 10 years focus on with PG, so they could competently pick something up from here and run with it? (Might be a question for IRC, Slack or the mailinglists.)
Thanks very much for mentioning that you are in Russia in a previous comment :) this gave me more bits of entropy to throw at Google and found some potentially interesting results.
First is https://www.postgresql.org/message-id/CANNMO++6tPiwBv2OKcy-H..., which suggests that Oracle is losing its ground there, with people switching to alternatives like PG.
Indeed Yandex switched recently, and it hit the front page of HN: https://news.ycombinator.com/item?id=12489055
So... this brought up a new idea that could be very interesting: you could specialize in Oracle-to-PostgreSQL migrations! This may well be a very worthwhile investment of time; large installations that need Everything And Especially All The Details® to Just Work And Simply Never Ever Fall Over™ are naturally going to be more than happy throwing you piles of money. I imagine that even in an assistant or entry-level position (being pragmatic; no insult intended) the associated portions allocated to you from said piles of money may still be appreciable. (Something I think about a lot is "where does everything scale so much it leaks tons of money?" :D)
Other resources that may be relevant:
http://postgresql.ru.net/
https://www.meetup.com/postgresqlrussia/
https://www.meetup.com/postgresqlrussia/events/past/
NB, the Russian link at https://www.postgresql.org/community/international/ is broken and appears to have been made redundant by the meetup links above.