Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I have a cluster of PostgreSQL nodes using streaming replication and running on RHEL 7. I plan to add new nodes running on RHEL 8, still using the same PostgreSQL version (12.7). Is mixing OS versions in a cluster a problem?
In general, streaming replication only works between the same OS and OS version.
While replicating between RHEL 7 and RHEL 8 might technically work, you might run into sever problems, e.g. because of different locale data which can lead to incorrect query results on the standby server.
I would not risk this. You should keep all servers at the same OS versions and patch level.
Logical replication on the other hand can be used to replicate between different operating systems (e.g. even from Linux to Windows). But that will require more setup and isn't really suitable if you want to replicate many databases that contain many schemas.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
PostgreSQL 11 works more efficiently in debian or redhat. Accordingly, I will choose a server and plan training. What are the advantages and disadvantages. Which operating system does the Postgres committee like?
There is no PostgreSQL committee. There is core, but they don't determine which operating systems are supported.
From the documentation (you probably read that):
A platform (that is, a CPU architecture and operating system combination) is considered supported by the PostgreSQL development community if the code contains provisions to work on that platform and it has recently been verified to build and pass its regression tests on that platform. Currently, most testing of platform compatibility is done automatically by test machines in the PostgreSQL Build Farm. If you are interested in using PostgreSQL on a platform that is not represented in the build farm, but on which the code works or can be made to work, you are strongly encouraged to set up a build farm member machine so that continued compatibility can be assured.
In general, PostgreSQL can be expected to work on these CPU architectures: x86, x86_64, IA64, PowerPC, PowerPC 64, S/390, S/390x, Sparc, Sparc 64, ARM, MIPS, MIPSEL, and PA-RISC. Code support exists for M68K, M32R, and VAX, but these architectures are not known to have been tested recently. It is often possible to build on an unsupported CPU type by configuring with --disable-spinlocks, but performance will be poor.
PostgreSQL can be expected to work on these operating systems: Linux (all recent distributions), Windows (Win2000 SP4 and later), FreeBSD, OpenBSD, NetBSD, macOS, AIX, HP/UX, and Solaris. Other Unix-like systems may also work but are not currently being tested. In most cases, all CPU architectures supported by a given operating system will work.
The majority of hackers use Linux, but there are people who develop on FreeBSD, MacOS or Windows.
If you know that PostgreSQL works most efficiently on certain Linux distributions, you know more than I do.
When choosing an operating system for PostgreSQL, I would proceed like this:
List the operating systems you are familiar with (or for which your organization has skilled administrators).
Exclude all operating systems for which there is not more than one animal in the buildfarm.
Exclude Windows.
Then pick any of these.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have installed and configured avahi-daemon and samba on Centos 6.6 and it's working when I am testing it from an Ubuntu machine. e.g.: ping myhostname.local or smb://myhostname.local
However, when I try from a windows machine, neither samba works nor I can ping it via ping myhostname
Can anyone please explain me the possible difference between what Windows does and what Ubuntu does.
Besides, it would be great if Windows could list my server when browsing network, but I don't know if I should enable something like a broadcast or just normal configuration is adequate.
Thanks a log in advance.
I've just post an answer to the same question on serverfault:
https://serverfault.com/questions/711619/centos-7-avahi-doesnt-resolve-from-windows-machines
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
the question is rather simple but I cannot hunt down the answer . I have an Ubuntu 14.04 LTS running on a vmware . For some testing purpose I need to launch another Ubuntu 14.04 LTS iso . I would like to know if I can use the same existing ISO i have for my older vmware install or will it screw up my old install ?
Using the existing ISO should be fine. Think of it like installing Ubuntu on 2 different computers with the same installation CD.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I have followed every step as given here. I installed all the servers and libraries but when I set the PostgreSQL server it hangs stating the follows on the terminal
LOG: database system was shut down at 2014-01-22 01:53:52 UTC
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
What to do?
I assume you're referring to these lines:
Finally, start up the server.
$ sudo -u postgres postgres -D /usr/local/pgsql/data
If so, that starts the PostgreSQL server in blocking mode. It is running. It won't exit until told to, and that terminal won't return. It sounds like you'd prefer it to exit and keep running in the background, in which case you should use pg_ctl to start the server instead.
The bigger problem is that those instructions are pretty stupid. You shouldn't be initdb'ing a new cluster and starting a new server; you almost certainly have one installed and running. It's hard to say, since you didn't say how you installed PostgreSQL, what OS you're on, what PostgreSQL version you have, etc.
In general, though, you should be connecting to your existing PostgreSQL install. Use that, don't initdb a new one. That's why the guide you were reading says:
This section may be unnecessary on your system. Check if your installation of postgres created a default database and start scripts for you.
Since you're using a stock Ubuntu install, please start by reading the Ubuntu introduction to PostgreSQL.
Then follow the setup guide starting at "create the database".
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I'm maintaining a simple web site written in Perl in my copious free time, and I don't want do my coding on the live website any more, instead checking if the changes work on a local machine first.
As far as I can tell, the web site runs on apache.
Should I install apache on my local machine, or are there simpler (but well documented!) options more suited to a development box?
Related question: How can I run Perl on web servers? , but seems to be talking about a production box, not a development box.
XAMPP is an excellent package for precisely this purpose. It includes Apache, MySQL, PHP, Perl, and other tools, all pre-configured to run on your local machine. I use it for WordPress, but I expect that it would be equally good for Perl CGI development.
I use it on Windows. It is also available for Linux and Mac.
Hat tip to Kenosis, who mentioned XAMPP first. I didn't see that at the time.