1. Home
2. Questions
3. Tags
5. Users
6. Jobs
7. Companies
8. Unanswered
Teams

Ask questions, find answers and collaborate at work with Stack Overflow for Teams.
Try Teams for free Explore Teams
Teams
Ask questions, find answers and collaborate at work with Stack Overflow for Teams. Explore Teams

Return to Question

Post Closed as "Not suitable for this site" by mustaccio, Marcello Miorelli, nbk, John K. N., Hannah Vernon♦

occurred yesterday

Typo fix

Source Link

edited Nov 23 at 18:49

1
2

Update. During today's apt purgeing, I have accidentally purgepurged the package postgresql-12. Then a screen showed up, and I select there not to remove configuration, as far as I can remember the question. Lucky me, postgresql.conf of v12 is still there, even though, confusingly to me, apt purge seemed to have processed it successfully. I'd rather not test all the above again if I'd not have a specific reason to do it. For now I just assume all the errors, et cetera, should be the same.

Update. During today's apt purgeing, I have accidentally purge the package postgresql-12. Then a screen showed up, and I select there not to remove configuration, as far as I can remember the question. Lucky me, postgresql.conf of v12 is still there, even though, confusingly to me, apt purge seemed to have processed it successfully. I'd rather not test all the above again if I'd not have a specific reason to do it. For now I just assume all the errors, et cetera, should be the same.

Update. During today's apt purgeing, I have accidentally purged the package postgresql-12. Then a screen showed up, and I select there not to remove configuration, as far as I can remember the question. Lucky me, postgresql.conf of v12 is still there, even though, confusingly to me, apt purge seemed to have processed it successfully. I'd rather not test all the above again if I'd not have a specific reason to do it. For now I just assume all the errors, et cetera, should be the same.

Clarification

Source Link

edited Nov 23 at 18:46

1
2

Update. During today's apt purgeing, I have accidentally purge the package postgresql-12. Then a screen showed up, and I select there not to remove configuration, as far as I can remember the question. Lucky me, postgresql.conf of v12 is still there, even though, confusingly to me, apt purge seemed to have processed it successfully. I'd rather not test all the above again if I'd not have a specific reason to do it. For now I just assume all the errors, et cetera, should be the same.

Update. During today's apt purgeing, I have accidentally purge the package postgresql-12. Then a screen showed up, and I select there not to remove configuration, as far as I can remember the question. Lucky me, postgresql.conf of v12 is still there, even though, confusingly to me, apt purge seemed to have processed it successfully. I'd rather not test all the above again if I'd not have a specific reason to do it.

Update. During today's apt purgeing, I have accidentally purge the package postgresql-12. Then a screen showed up, and I select there not to remove configuration, as far as I can remember the question. Lucky me, postgresql.conf of v12 is still there, even though, confusingly to me, apt purge seemed to have processed it successfully. I'd rather not test all the above again if I'd not have a specific reason to do it. For now I just assume all the errors, et cetera, should be the same.

apt purge update

Source Link

edited Nov 23 at 18:44

1
2

Update. During today's apt purgeing, I have accidentally purge the package postgresql-12. Then a screen showed up, and I select there not to remove configuration, as far as I can remember the question. Lucky me, postgresql.conf of v12 is still there, even though, confusingly to me, apt purge seemed to have processed it successfully. I'd rather not test all the above again if I'd not have a specific reason to do it.

Update. During today's apt purgeing, I have accidentally purge the package postgresql-12. Then a screen showed up, and I select there not to remove configuration, as far as I can remember the question. Lucky me, postgresql.conf of v12 is still there, even though, confusingly to me, apt purge seemed to have processed it successfully. I'd rather not test all the above again if I'd not have a specific reason to do it.

postgresql-12 package update

Source Link

edited Nov 22 at 17:37

1
2

Loading

Readability improvement

Source Link

edited Nov 22 at 17:25

1
2

Loading

unix_socket_directories and pg_wrapper update

Source Link

edited Nov 22 at 17:24

1
2

Loading

Ambiguity fix

Source Link

edited Nov 21 at 20:27

1
2

Loading

unix_socket_directories update

Source Link

edited Nov 21 at 20:19

1
2

Loading

Another psql version lookup addition

Source Link

edited Nov 21 at 19:52

1
2

Loading

Socket file search results and explicit socket providing psql command addition

Source Link

edited Nov 21 at 19:12

1
2

Loading

Socket addition

Source Link

edited Nov 21 at 17:55

1
2

Loading

Clusters ports and statuses table addition

Source Link

edited Nov 21 at 16:08

1
2

Loading

Utility name and command name difference emphasis

Source Link

edited Nov 20 at 20:49

1
2

Loading

pg_lsclusters output and port additions

Source Link

edited Nov 20 at 19:27

1
2

Loading

Server restarting command addition

Source Link

edited Nov 20 at 17:47

1
2

Loading

Simplified table addition

Source Link

edited Nov 20 at 16:08

1
2

Loading

Title grammar fix

Link

edited Nov 19 at 20:52

1
2

Loading

Source Link

asked Nov 19 at 20:47

1
2

Loading