exact information. If you are using a prepackaged distribution that starts the database server at boot time, you should try to find out how that is done. • Anything you did at all differently from the latest before you install the new files: pg_ctl stop On systems that have PostgreSQL started at boot time, there is probably a start-up file that will accomplish the same thing. For example, on a Red require root privileges. Different systems have different conventions for starting up daemons at boot time. Many systems have a file /etc/rc.local or /etc/rc.d/rc.local. Others use rc.d directories. Whatever

exact information. If you are using a prepackaged distribution that starts the database server at boot time, you should try to find out how that is done. • Anything you did at all differently from the latest before you install the new files: pg_ctl stop On systems that have PostgreSQL started at boot time, there is probably a start-up file that will accomplish the same thing. For example, on a Red require root privileges. Different systems have different conventions for starting up daemons at boot time. Many systems have a file /etc/rc.local or /etc/rc.d/rc.local. Others use rc.d directories. Whatever

exact information. If you are using a prepackaged distribution that starts the database server at boot time, you should try to find out how that is done. • Anything you did at all differently from the the latest before you install the new files: pg_ctl stop On systems that have PostgreSQL started at boot time, there is probably a start-up file that will accomplish the same thing. For example, on a Red require root privileges. Different systems have different conventions for starting up daemons at boot time. Many systems have a file /etc/rc.local or /etc/rc.d/rc.local. Others use rc.d directories. Whatever

exact information. If you are using a prepackaged distribution that starts the database server at boot time, you should try to find out how that is done. • Anything you did at all differently from the the latest before you install the new files: pg_ctl stop On systems that have PostgreSQL started at boot time, there is probably a start-up file that will accomplish the same thing. For example, on a Red require root privileges. Different systems have different conventions for starting up daemons at boot time. Many systems have a file /etc/rc.local or /etc/rc.d/rc.local. Others use rc.d directories. Whatever

exact information. If you are using a prepackaged distribution that starts the database server at boot time, you should try to find out how that is done. • Anything you did at all differently from the require root privileges. Different systems have different conventions for starting up daemons at boot time. Many systems have a file /etc/rc.local or /etc/rc.d/rc.local. Others use init.d or rc.d directories /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages It is also possible to provide these settings at boot time using kernel parameters such as hugepagesz=2M hugepages=3170. Sometimes the kernel is not able

exact information. If you are using a prepackaged distribution that starts the database server at boot time, you should try to find out how that is done. • Anything you did at all differently from the the downtime. 2. Shut down the old server: pg_ctl stop On systems that have PostgreSQL started at boot time, there is probably a start-up file that will accomplish the same thing. For example, on a Red require root privileges. Different systems have different conventions for starting up daemons at boot time. Many systems have a file /etc/rc.local or /etc/rc.d/rc.local. Others use rc.d directories. Whatever

exact information. If you are using a prepackaged distribution that starts the database server at boot time, you should try to find out how that is done. • Anything you did at all differently from the the downtime. 2. Shut down the old server: pg_ctl stop On systems that have PostgreSQL started at boot time, there is probably a start-up file that will accomplish the same thing. For example, on a Red require root privileges. Different systems have different conventions for starting up daemons at boot time. Many systems have a file /etc/rc.local or /etc/rc.d/rc.local. Others use rc.d directories. Whatever

exact information. If you are using a prepackaged distribution that starts the database server at boot time, you should try to find out how that is done. • Anything you did at all differently from the require root privileges. Different systems have different conventions for starting up daemons at boot time. Many systems have a file /etc/rc.local or /etc/rc.d/rc.local. Others use init.d or rc.d directories /sys/kernel/mm/hugepages/hugepages-2048kB/ nr_hugepages It is also possible to provide these settings at boot time using kernel parameters such as hugepagesz=2M hugepages=3170. Sometimes the kernel is not able

exact information. If you are using a prepackaged distribution that starts the database server at boot time, you should try to find out how that is done. • Anything you did at all differently from the require root privileges. Different systems have different conventions for starting up daemons at boot time. Many systems have a file /etc/rc.local or /etc/rc.d/rc.local. Others use init.d or rc.d directories These semaphore-related settings are read-only as far as sysctl is concerned, but can be set in /boot/loader.conf: kern.ipc.semmni=256 kern.ipc.semmns=512 After modifying that file, a reboot is required

exact information. If you are using a prepackaged distribution that starts the database server at boot time, you should try to find out how that is done. • Anything you did at all differently from the require root privileges. Different systems have different conventions for starting up daemons at boot time. Many systems have a file /etc/rc.local or /etc/rc.d/rc.local. Others use init.d or rc.d directories These semaphore-related settings are read-only as far as sysctl is concerned, but can be set in / boot/loader.conf: kern.ipc.semmni=256 kern.ipc.semmns=512 After modifying that file, a reboot is required