学习目标
1.从操作系统层面查看数据库进程和线程,判断数据库是否启动。
2.使用gs_ctl工具查看数据库状态,判断数据库是否启动。
3.使用gs_ctl 查看数据文件的目录
4.从环境变量查看数据文件的目录
5.在gsql中查看数据文件目录、数据库版本
实操结果
1.从操作系统层面查看数据库进程和线程,判断数据库是否启动。
omm 1 0 0 14:58 ? 00:00:00 gaussdb omm 383 377 0 14:59 pts/0 00:00:00 grep gauss
复制
2.使用gs_ctl工具查看数据库状态,判断数据库是否启动。
\[2022-11-24 14:59:34.641\]\[386\]\[\]\[gs\_ctl\]: gs\_ctl status,datadir is /var/lib/opengauss/data gs\_ctl: server is running (PID: 1) /usr/local/opengauss/bin/gaussdb
复制
3.使用gs_ctl 查看数据文件的目录
\[2022-11-24 14:59:42.532\]\[390\]\[\]\[gs\_ctl\]: gs\_ctl notify ,datadir is /var/lib/opengauss/data \[2022-11-24 14:59:42.532\]\[390\]\[\]\[gs\_ctl\]: the parameter of notify must be specified
复制
4.从环境变量查看数据文件的目录
\# ~/.bashrc: executed by bash(1) for non-login shells. \# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) \# for examples \# If not running interactively, don't do anything case $- in \*i\*) ;; \*) return;; esac \# don't put duplicate lines or lines starting with space in the history. \# See bash(1) for more options HISTCONTROL=ignoreboth \# append to the history file, don't overwrite it shopt -s histappend \# for setting history length see HISTSIZE and HISTFILESIZE in bash(1) HISTSIZE=1000 HISTFILESIZE=2000 \# check the window size after each command and, if necessary, \# update the values of LINES and COLUMNS. shopt -s checkwinsize \# If set, the pattern "\*\*" used in a pathname expansion context will \# match all files and zero or more directories and subdirectories. #shopt -s globstar \# make less more friendly for non-text input files, see lesspipe(1) #\[ -x /usr/bin/lesspipe \] && eval "$(SHELL=/bin/sh lesspipe)" \# set variable identifying the chr3\[00m\\\]\\$ ' else PS1='${debian\_chroot:+($debian\_chroot)}\\u@\\h:\\w\\$ ' fi unset color\_prompt force\_color\_prompt \# If this is an xterm set the title to user@host:dir case "$TERM" in xterm\*|rxvt\*) PS1="\\\[\\e\]0;${debian\_chroot:+($debian\_chroot)}\\u@\\h: \\w\\a\\\]$PS1" ;; \*) ;; esac \# enable color support of ls and also add handy aliases if \[ -x /usr/bin/dircolors \]; then test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)" alias ls='ls --color=auto' #alias dir='dir --color=auto' #alias vdir='vdir --color=auto' #alias grep='grep --color=auto' #alias fgrep='fgrep --color=auto' #alias egrep='egrep --color=auto' fi \# colored GCC warnings and errors #export GCC\_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01' \# some more ls aliases #alias ll='ls -l' #alias la='ls -A' #alias l='ls -CF' \# Alias definitions. \# You may want to put all your additions into a separate file like \# ~/.bashoot you work in (used in the prompt below) if \[ -z "${debian\_chroot:-}" \] && \[ -r /etc/debian\_chroot \]; then debian\_chroot=$(cat /etc/debian\_chroot) fi \# set a fancy prompt (non-color, unless we know we "want" color) case "$TERM" in xterm-color|\*-256color) color\_prompt=yes;; esac \# uncomment for a colored prompt, if the terminal has the capability; turned \# off by default to not distract the user: the focus in a terminal window \# should be on the output of commands, not on the prompt #force\_color\_prompt=yes if \[ -n "$force\_color\_prompt" \]; then if \[ -x /usr/bin/tput \] && tput setaf 1 >&/dev/null; then \# We have color support; assume it's compliant with Ecma-48 \# (ISO/IEC-6429). (Lack of such support is extremely rare, and such \# a case would tend to support setf rather than setaf.) color\_prompt=yes else color\_prompt= fi fi if \[ "$color\_prompt" = yes \]; then PS1='${debian\_chroot:+($debian\_chroot)}\\\[\\033\[01;32m\\\]\\u@\\h\\\[\\033\[00m\\\]:\\\[\\033\[01;34m\\\]\\w\\\[\\03\_aliases, instead of adding them here directly. \# See /usr/share/doc/bash-doc/examples in the bash-doc package. if \[ -f ~/.bash\_aliases \]; then . ~/.bash\_aliases fi \# enable programmable completion features (you don't need to enable \# this, if it's already enabled in /etc/bash.bashrc and /etc/profile \# sources /etc/bash.bashrc). if ! shopt -oq posix; then if \[ -f /usr/share/bash-completion/bash\_completion \]; then . /usr/share/bash-completion/bash\_completion elif \[ -f /etc/bash\_completion \]; then . /etc/bash\_completion fi fi export GAUSSHOME=/usr/local/opengauss export PATH=$GAUSSHOME/bin:$PATH export LD\_LIBRARY\_PATH=$GAUSSHOME/lib:$LD\_LIBRARY\_PATH export PGDATA=/var/lib/opengauss/data 在gsql中查看数据文件目录、数据库版本 omm@modb:~$ gsql -r gsql ((openGauss 3.0.0 build 02c14696) compiled at 2022-04-01 18:12:00 commit 0 last mr ) Non-SSL connection (SSL connection is recommended when requiring high-security) Type "help" for help. omm=# show data\_directoryomm-# ^C omm=# show data\_directory ; omm=# data\_directory \------------------------- /var/lib/opengauss/data (1 row) omm=# select version(); (openGauss 3.0.0 build 02c14696) compiled at 2022-04-01 18:12:00 commit 0 last mr on aarch64-unknown-linux-gnu, compiled by g++ (GCC) 7.3.0, 64-bit (1 row)
复制
熟练掌握通过gs_ctl的相关用法```language
复制
最后修改时间:2022-11-28 20:30:38
「喜欢这篇文章,您的关注和赞赏是给作者最好的鼓励」
关注作者
【版权声明】本文为墨天轮用户原创内容,转载时必须标注文章的来源(墨天轮),文章链接,文章作者等基本信息,否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容,欢迎发送邮件至:contact@modb.pro进行举报,并提供相关证据,一经查实,墨天轮将立刻删除相关内容。
评论
您的sql语句要用markdown来编辑哦
2年前

评论
相关阅读
openGauss荣获中国软件行业协会多奖项,技术升级再创行业新高度
openGauss
555次阅读
2025-04-30 14:30:58
MogDB 发布更新,解决 openGauss 数据库在长事务情况下Ustore表膨胀问题
MogDB
307次阅读
2025-04-17 10:41:41
MogDB 发布更新,解决 openGauss 数据库在长事务情况下Ustore表膨胀问题
云和恩墨
201次阅读
2025-04-16 09:52:02
GitCode 成 openGauss 新归宿,国产开源数据库里程碑事件
严少安
172次阅读
2025-04-27 11:37:53
荣誉时刻!openGauss认证证书快递已发,快来看看谁榜上有名!
墨天轮小教习
162次阅读
2025-04-23 17:39:13
单个执行机并行执行MySQL到openGauss数据迁移子任务
Clipnosis
151次阅读
2025-04-30 16:39:58
openGauss6.0.0适配操作系统自带的软件,不依赖三方库
来杯拿铁
96次阅读
2025-04-18 10:49:53
Postgresql数据库单个Page最多存储多少行数据
maozicb
92次阅读
2025-04-23 16:02:19
openGauss新特性 | openGauss-DataVec向量数据库特性介绍
openGauss
65次阅读
2025-04-17 10:41:47
RISC-V 首迎 openGauss 7.0.0-RC1 全量版适配!数据库核心功能完整落地开源架构
openGauss
49次阅读
2025-04-16 10:33:59