[转]What are mode and status columns under gp_segment_configuration table
February 16, 2017 10:39
Goal
In this article we will try to understand and answer to the below two question.
How to understand the segment mode and status of gp_segment_configuration table ?
What does 'c', 'r', 's' mean in mode column of gp_segment_configuration table?
Solution
This article explains the meaning of 'c', 'r', 's' in the mode column, and the meaning of 'u', 'd' in the status column of gp_segment_configuration table.
The meaning is explained in two examples.
Example 1: Kill a mirror instance
-- This is a healthy instance, and all segments are up and running as their perferred roles. The segments' status is 'u' (up), mode is 's' (synchronized). 'synchronized' means all changes happening in primary instance are already synchronized in mirror instances, so in this condition, if the primary or mirror instance is down, there will be no data loss since the corresponding mirror/primary instance already has the same data.
template1=# select * from gp_segment_configuration;
dbid " content " role " preferred_role " mode " status " port " hostname " address " replication_port " san_mounts
------+---------+------+----------------+------+--------+-------+----------+---------+------------------+------------
1 " -1 " p " p " s " u " 5582 " mdw " mdw " "
2 " 0 " p " p " s " u " 48212 " sdw1 " sdw1-1 " 42182 "
4 " 2 " p " p " s " u " 48212 " sdw3 " sdw3-1 " 42182 "
3 " 1 " p " p " s " u " 48213 " sdw1 " sdw1-2 " 42183 "
5 " 3 " p " p " s " u " 48213 " sdw3 " sdw3-2 " 42183 "
10 " 0 " m " m " s " u " 58212 " sdw3 " sdw3-2 " 52820 "
11 " 1 " m " m " s " u " 58213 " sdw3 " sdw3-1 " 52821 "
12 " 2 " m " m " s " u " 58212 " sdw4 " sdw4-2 " 52820 "
13 " 3 " m " m " s " u " 58213 " sdw4 " sdw4-1 " 52821 "
6 " 4 " p " p " s " u " 48212 " sdw4 " sdw4-1 " 42182 "
14 " 4 " m " m " s " u " 58212 " sdw5 " sdw5-2 " 52820 "
7 " 5 " p " p " s " u " 48213 " sdw4 " sdw4-2 " 42183 "
15 " 5 " m " m " s " u " 58213 " sdw5 " sdw5-1 " 52821 "
8 " 6 " p " p " s " u " 48212 " sdw5 " sdw5-1 " 42182 "
16 " 6 " m " m " s " u " 58212 " sdw1 " sdw1-2 " 52820 "
17 " 7 " m " m " s " u " 58213 " sdw1 " sdw1-1 " 52821 "
9 " 7 " p " p " s " u " 48213 " sdw5 " sdw5-2 " 42183 "
(17 rows)
-- Run SSH to one of the segment server, for example, sdw1, and kill a mirror instance, for example, with dbid 16.
[gpadmin@mdw alice]$ ssh sdw1
Last login: Sun Aug 14 21:54:02 2011 from mdw
[gpadmin@sdw1 ~]$ ps -ef " grep az " grep 4111
gpadmin 879 1 0 Aug07 ? 00:00:04 /usr/local/greenplum-db-4.1.1.1_JL/bin/postgres -D /data/azprimary4111/gpsegaz41111 -i -p 48213 --silent-mode=true -M quiescent -b 3 -C 1 -z 8
gpadmin 881 1 0 Aug07 ? 00:00:03 /usr/local/greenplum-db-4.1.1.1_JL/bin/postgres -D /data/azprimary4111/gpsegaz41110 -i -p 48212 --silent-mode=true -M quiescent -b 2 -C 0 -z 8
gpadmin 882 1 0 Aug07 ? 00:00:00 /usr/local/greenplum-db-4.1.1.1_JL/bin/postgres -D /data/azmirror4111/gpsegaz41117 -i -p 58213 --silent-mode=true -M quiescent -b 17 -C 7 -z 8
gpadmin 883 1 0 Aug07 ? 00:00:00 /usr/local/greenplum-db-4.1.1.1_JL/bin/postgres -D /data/azmirror4111/gpsegaz41116 -i -p 58212 --silent-mode=true -M quiescent -b 16 -C 6 -z 8
[gpadmin@sdw1 ~]$ kill 883
[gpadmin@sdw1 ~]$ ps -ef " grep az " grep 4111
gpadmin 879 1 0 Aug07 ? 00:00:04 /usr/local/greenplum-db-4.1.1.1_JL/bin/postgres -D /data/azprimary4111/gpsegaz41111 -i -p 48213 --silent-mode=true -M quiescent -b 3 -C 1 -z 8
gpadmin 881 1 0 Aug07 ? 00:00:03 /usr/local/greenplum-db-4.1.1.1_JL/bin/postgres -D /data/azprimary4111/gpsegaz41110 -i -p 48212 --silent-mode=true -M quiescent -b 2 -C 0 -z 8
gpadmin 882 1 0 Aug07 ? 00:00:00 /usr/local/greenplum-db-4.1.1.1_JL/bin/postgres -D /data/azmirror4111/gpsegaz41117 -i -p 58213 --silent-mode=true -M quiescent -b 17 -C 7 -z 8
[gpadmin@sdw1 ~]$ exit
logout
-- Check the gpstate and gp_segment_configuration table again.
[gpadmin@mdw alice]$ gpstate
20110815:13:27:16:gpstate:mdw:gpadmin-[INFO]:-Starting gpstate with args:
20110815:13:27:16:gpstate:mdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.1.1.1 build 1'
20110815:13:27:16:gpstate:mdw:gpadmin-[INFO]:-Obtaining Segment details from master...
20110815:13:27:16:gpstate:mdw:gpadmin-[INFO]:-Gathering data from segments...
.
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:-Greenplum instance status summary
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:-----------------------------------------------------
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Master instance = Active
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Master standby = No master standby configured
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total segment instance count from metadata = 16
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:-----------------------------------------------------
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Primary Segment Status
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:-----------------------------------------------------
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total primary segments = 8
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total primary segment valid (at master) = 8
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total primary segment failures (at master) = 0
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number of postmaster.pid files missing = 0
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number of postmaster.pid files found = 8
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number of postmaster.pid PIDs missing = 0
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number of postmaster.pid PIDs found = 8
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number of /tmp lock files missing = 0
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number of /tmp lock files found = 8
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number postmaster processes missing = 0
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number postmaster processes found = 8
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:-----------------------------------------------------
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Mirror Segment Status
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:-----------------------------------------------------
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total mirror segments = 8
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total mirror segment valid (at master) = 8
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total mirror segment failures (at master) = 0
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number of postmaster.pid files missing = 0
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number of postmaster.pid files found = 8
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number of postmaster.pid PIDs missing = 0
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number of postmaster.pid PIDs found = 8
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number of /tmp lock files missing = 0
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number of /tmp lock files found = 8
20110815:13:27:17:gpstate:mdw:gpadmin-[WARNING]:-Total number postmaster processes missing = 1 <<<<<<<<
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number postmaster processes found = 7
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number mirror segments acting as primary segments = 0
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:- Total number mirror segments acting as mirror segments = 8
20110815:13:27:17:gpstate:mdw:gpadmin-[INFO]:----------------------------------------------------- [gpadmin@mdw alice]$ psql template1
Timing is on.
psql (8.2.15)
Type "help" for help. template1=# select * from gp_segment_configuration;
dbid " content " role " preferred_role " mode " status " port " hostname " address " replication_port " san_mounts
------+---------+------+----------------+------+--------+-------+----------+---------+------------------+------------
1 " -1 " p " p " s " u " 5582 " mdw " mdw " "
2 " 0 " p " p " s " u " 48212 " sdw1 " sdw1-1 " 42182 "
4 " 2 " p " p " s " u " 48212 " sdw3 " sdw3-1 " 42182 "
3 " 1 " p " p " s " u " 48213 " sdw1 " sdw1-2 " 42183 "
5 " 3 " p " p " s " u " 48213 " sdw3 " sdw3-2 " 42183 "
10 " 0 " m " m " s " u " 58212 " sdw3 " sdw3-2 " 52820 "
11 " 1 " m " m " s " u " 58213 " sdw3 " sdw3-1 " 52821 "
12 " 2 " m " m " s " u " 58212 " sdw4 " sdw4-2 " 52820 "
13 " 3 " m " m " s " u " 58213 " sdw4 " sdw4-1 " 52821 "
6 " 4 " p " p " s " u " 48212 " sdw4 " sdw4-1 " 42182 "
14 " 4 " m " m " s " u " 58212 " sdw5 " sdw5-2 " 52820 "
7 " 5 " p " p " s " u " 48213 " sdw4 " sdw4-2 " 42183 "
15 " 5 " m " m " s " u " 58213 " sdw5 " sdw5-1 " 52821 "
8 " 6 " p " p " c " u " 48212 " sdw5 " sdw5-1 " 42182 "
16 " 6 " m " m " s " d " 58212 " sdw1 " sdw1-2 " 52820 "
17 " 7 " m " m " s " u " 58213 " sdw1 " sdw1-1 " 52821 "
9 " 7 " p " p " s " u " 48213 " sdw5 " sdw5-2 " 42183 "
(17 rows)
You can see that the instance with port=58212 status is 'd' (down), its primary instance status is still 'u', but the mode is changed 'c' (change tracking). At this time, the primary instance is logging all transactional changes made to the database, these are tracked via the files available at $SEG_DATA_DIRECTORY/pg_changetracking location, but its not synchronized to the mirror instance because it is down.
-- Run gprecoverseg to recover the down instance.
To recover ths mirror instance, run the gprecoverseg command then check the status again. You can see both instance are up now, but the mode is 'r' (resynchronization), which means the resynchronization process is applying changes that is recorded in change tracking log file to mirror segment.
template1=# select * from gp_segment_configuration;
dbid " content " role " preferred_role " mode " status " port " hostname " address " replication_port " san_mounts
------+---------+------+----------------+------+--------+-------+----------+---------+------------------+------------
1 " -1 " p " p " s " u " 5582 " mdw " mdw " "
2 " 0 " p " p " s " u " 48212 " sdw1 " sdw1-1 " 42182 "
4 " 2 " p " p " s " u " 48212 " sdw3 " sdw3-1 " 42182 "
3 " 1 " p " p " s " u " 48213 " sdw1 " sdw1-2 " 42183 "
5 " 3 " p " p " s " u " 48213 " sdw3 " sdw3-2 " 42183 "
10 " 0 " m " m " s " u " 58212 " sdw3 " sdw3-2 " 52820 "
11 " 1 " m " m " s " u " 58213 " sdw3 " sdw3-1 " 52821 "
12 " 2 " m " m " s " u " 58212 " sdw4 " sdw4-2 " 52820 "
13 " 3 " m " m " s " u " 58213 " sdw4 " sdw4-1 " 52821 "
6 " 4 " p " p " s " u " 48212 " sdw4 " sdw4-1 " 42182 "
14 " 4 " m " m " s " u " 58212 " sdw5 " sdw5-2 " 52820 "
7 " 5 " p " p " s " u " 48213 " sdw4 " sdw4-2 " 42183 "
15 " 5 " m " m " s " u " 58213 " sdw5 " sdw5-1 " 52821 "
17 " 7 " m " m " s " u " 58213 " sdw1 " sdw1-1 " 52821 "
9 " 7 " p " p " s " u " 48213 " sdw5 " sdw5-2 " 42183 "
8 " 6 " p " p " r " u " 48212 " sdw5 " sdw5-1 " 42182 "
16 " 6 " m " m " r " u " 58212 " sdw1 " sdw1-2 " 52820 "
(17 rows)
After a while, check the table again, you can see both of them are synchronized.
template1=# select * from gp_segment_configuration;
dbid " content " role " preferred_role " mode " status " port " hostname " address " replication_port " san_mounts
------+---------+------+----------------+------+--------+-------+----------+---------+------------------+------------
1 " -1 " p " p " s " u " 5582 " mdw " mdw " "
2 " 0 " p " p " s " u " 48212 " sdw1 " sdw1-1 " 42182 "
4 " 2 " p " p " s " u " 48212 " sdw3 " sdw3-1 " 42182 "
3 " 1 " p " p " s " u " 48213 " sdw1 " sdw1-2 " 42183 "
5 " 3 " p " p " s " u " 48213 " sdw3 " sdw3-2 " 42183 "
10 " 0 " m " m " s " u " 58212 " sdw3 " sdw3-2 " 52820 "
11 " 1 " m " m " s " u " 58213 " sdw3 " sdw3-1 " 52821 "
12 " 2 " m " m " s " u " 58212 " sdw4 " sdw4-2 " 52820 "
13 " 3 " m " m " s " u " 58213 " sdw4 " sdw4-1 " 52821 "
6 " 4 " p " p " s " u " 48212 " sdw4 " sdw4-1 " 42182 "
14 " 4 " m " m " s " u " 58212 " sdw5 " sdw5-2 " 52820 "
7 " 5 " p " p " s " u " 48213 " sdw4 " sdw4-2 " 42183 "
15 " 5 " m " m " s " u " 58213 " sdw5 " sdw5-1 " 52821 "
17 " 7 " m " m " s " u " 58213 " sdw1 " sdw1-1 " 52821 "
9 " 7 " p " p " s " u " 48213 " sdw5 " sdw5-2 " 42183 "
8 " 6 " p " p " s " u " 48212 " sdw5 " sdw5-1 " 42182 "
16 " 6 " m " m " s " u " 58212 " sdw1 " sdw1-2 " 52820 "
(17 rows)
Example 2: Kill a primary instance
-- Kill a primary instance with dbid=3.
template1=# select * from gp_segment_configuration;
dbid " content " role " preferred_role " mode " status " port " hostname " address " replication_port " san_mounts
------+---------+------+----------------+------+--------+-------+----------+---------+------------------+------------
1 " -1 " p " p " s " u " 5582 " mdw " mdw " "
2 " 0 " p " p " s " u " 48212 " sdw1 " sdw1-1 " 42182 "
4 " 2 " p " p " s " u " 48212 " sdw3 " sdw3-1 " 42182 "
5 " 3 " p " p " s " u " 48213 " sdw3 " sdw3-2 " 42183 "
10 " 0 " m " m " s " u " 58212 " sdw3 " sdw3-2 " 52820 "
12 " 2 " m " m " s " u " 58212 " sdw4 " sdw4-2 " 52820 "
13 " 3 " m " m " s " u " 58213 " sdw4 " sdw4-1 " 52821 "
6 " 4 " p " p " s " u " 48212 " sdw4 " sdw4-1 " 42182 "
14 " 4 " m " m " s " u " 58212 " sdw5 " sdw5-2 " 52820 "
7 " 5 " p " p " s " u " 48213 " sdw4 " sdw4-2 " 42183 "
15 " 5 " m " m " s " u " 58213 " sdw5 " sdw5-1 " 52821 "
17 " 7 " m " m " s " u " 58213 " sdw1 " sdw1-1 " 52821 "
9 " 7 " p " p " s " u " 48213 " sdw5 " sdw5-2 " 42183 "
8 " 6 " p " p " s " u " 48212 " sdw5 " sdw5-1 " 42182 "
16 " 6 " m " m " s " u " 58212 " sdw1 " sdw1-2 " 52820 "
3 " 1 " m " p " s " d " 48213 " sdw1 " sdw1-2 " 42183 "
11 " 1 " p " m " c " u " 58213 " sdw3 " sdw3-1 " 52821 "
(17 rows)
You can see the primary instance dbid=3 status is down now, its mirror instance is up, and the mode is change tracking.
-- Run gprecoverseg command again.
template1=# select * from gp_segment_configuration;
dbid " content " role " preferred_role " mode " status " port " hostname " address " replication_port " san_mounts
------+---------+------+----------------+------+--------+-------+----------+---------+------------------+------------
1 " -1 " p " p " s " u " 5582 " mdw " mdw " "
2 " 0 " p " p " s " u " 48212 " sdw1 " sdw1-1 " 42182 "
4 " 2 " p " p " s " u " 48212 " sdw3 " sdw3-1 " 42182 "
5 " 3 " p " p " s " u " 48213 " sdw3 " sdw3-2 " 42183 "
10 " 0 " m " m " s " u " 58212 " sdw3 " sdw3-2 " 52820 "
12 " 2 " m " m " s " u " 58212 " sdw4 " sdw4-2 " 52820 "
13 " 3 " m " m " s " u " 58213 " sdw4 " sdw4-1 " 52821 "
6 " 4 " p " p " s " u " 48212 " sdw4 " sdw4-1 " 42182 "
14 " 4 " m " m " s " u " 58212 " sdw5 " sdw5-2 " 52820 "
7 " 5 " p " p " s " u " 48213 " sdw4 " sdw4-2 " 42183 "
15 " 5 " m " m " s " u " 58213 " sdw5 " sdw5-1 " 52821 "
17 " 7 " m " m " s " u " 58213 " sdw1 " sdw1-1 " 52821 "
9 " 7 " p " p " s " u " 48213 " sdw5 " sdw5-2 " 42183 "
8 " 6 " p " p " s " u " 48212 " sdw5 " sdw5-1 " 42182 "
16 " 6 " m " m " s " u " 58212 " sdw1 " sdw1-2 " 52820 "
3 " 1 " m " p " r " u " 48213 " sdw1 " sdw1-2 " 42183 "
11 " 1 " p " m " r " u " 58213 " sdw3 " sdw3-1 " 52821 "
(17 rows)
After a while, they are synchronized
template1=# select * from gp_segment_configuration;
dbid " content " role " preferred_role " mode " status " port " hostname " address " replication_port " san_mounts
------+---------+------+----------------+------+--------+-------+----------+---------+------------------+------------
1 " -1 " p " p " s " u " 5582 " mdw " mdw " "
2 " 0 " p " p " s " u " 48212 " sdw1 " sdw1-1 " 42182 "
4 " 2 " p " p " s " u " 48212 " sdw3 " sdw3-1 " 42182 "
5 " 3 " p " p " s " u " 48213 " sdw3 " sdw3-2 " 42183 "
10 " 0 " m " m " s " u " 58212 " sdw3 " sdw3-2 " 52820 "
12 " 2 " m " m " s " u " 58212 " sdw4 " sdw4-2 " 52820 "
13 " 3 " m " m " s " u " 58213 " sdw4 " sdw4-1 " 52821 "
6 " 4 " p " p " s " u " 48212 " sdw4 " sdw4-1 " 42182 "
14 " 4 " m " m " s " u " 58212 " sdw5 " sdw5-2 " 52820 "
7 " 5 " p " p " s " u " 48213 " sdw4 " sdw4-2 " 42183 "
15 " 5 " m " m " s " u " 58213 " sdw5 " sdw5-1 " 52821 "
17 " 7 " m " m " s " u " 58213 " sdw1 " sdw1-1 " 52821 "
9 " 7 " p " p " s " u " 48213 " sdw5 " sdw5-2 " 42183 "
8 " 6 " p " p " s " u " 48212 " sdw5 " sdw5-1 " 42182 "
16 " 6 " m " m " s " u " 58212 " sdw1 " sdw1-2 " 52820 "
11 " 1 " p " m " s " u " 58213 " sdw3 " sdw3-1 " 52821 "
3 " 1 " m " p " s " u " 48213 " sdw1 " sdw1-2 " 42183 "
(17 rows)
-- Run the gprecoverseg -r command to bring the segment to its preferred role.
template1=# select * from gp_segment_configuration;
dbid " content " role " preferred_role " mode " status " port " hostname " address " replication_port " san_mounts
------+---------+------+----------------+------+--------+-------+----------+---------+------------------+------------
1 " -1 " p " p " s " u " 5582 " mdw " mdw " "
2 " 0 " p " p " s " u " 48212 " sdw1 " sdw1-1 " 42182 "
4 " 2 " p " p " s " u " 48212 " sdw3 " sdw3-1 " 42182 "
5 " 3 " p " p " s " u " 48213 " sdw3 " sdw3-2 " 42183 "
10 " 0 " m " m " s " u " 58212 " sdw3 " sdw3-2 " 52820 "
12 " 2 " m " m " s " u " 58212 " sdw4 " sdw4-2 " 52820 "
13 " 3 " m " m " s " u " 58213 " sdw4 " sdw4-1 " 52821 "
6 " 4 " p " p " s " u " 48212 " sdw4 " sdw4-1 " 42182 "
14 " 4 " m " m " s " u " 58212 " sdw5 " sdw5-2 " 52820 "
7 " 5 " p " p " s " u " 48213 " sdw4 " sdw4-2 " 42183 "
15 " 5 " m " m " s " u " 58213 " sdw5 " sdw5-1 " 52821 "
17 " 7 " m " m " s " u " 58213 " sdw1 " sdw1-1 " 52821 "
9 " 7 " p " p " s " u " 48213 " sdw5 " sdw5-2 " 42183 "
8 " 6 " p " p " s " u " 48212 " sdw5 " sdw5-1 " 42182 "
16 " 6 " m " m " s " u " 58212 " sdw1 " sdw1-2 " 52820 "
3 " 1 " p " p " r " u " 48213 " sdw1 " sdw1-2 " 42183 "
11 " 1 " m " m " r " u " 58213 " sdw3 " sdw3-1 " 52821 "
(17 rows)
After a while, they are back to their preferred roles, and synchronized:
template1=# select * from gp_segment_configuration;
dbid " content " role " preferred_role " mode " status " port " hostname " address " replication_port " san_mounts
------+---------+------+----------------+------+--------+-------+----------+---------+------------------+------------
1 " -1 " p " p " s " u " 5582 " mdw " mdw " "
2 " 0 " p " p " s " u " 48212 " sdw1 " sdw1-1 " 42182 "
4 " 2 " p " p " s " u " 48212 " sdw3 " sdw3-1 " 42182 "
5 " 3 " p " p " s " u " 48213 " sdw3 " sdw3-2 " 42183 "
10 " 0 " m " m " s " u " 58212 " sdw3 " sdw3-2 " 52820 "
12 " 2 " m " m " s " u " 58212 " sdw4 " sdw4-2 " 52820 "
13 " 3 " m " m " s " u " 58213 " sdw4 " sdw4-1 " 52821 "
6 " 4 " p " p " s " u " 48212 " sdw4 " sdw4-1 " 42182 "
14 " 4 " m " m " s " u " 58212 " sdw5 " sdw5-2 " 52820 "
7 " 5 " p " p " s " u " 48213 " sdw4 " sdw4-2 " 42183 "
15 " 5 " m " m " s " u " 58213 " sdw5 " sdw5-1 " 52821 "
17 " 7 " m " m " s " u " 58213 " sdw1 " sdw1-1 " 52821 "
9 " 7 " p " p " s " u " 48213 " sdw5 " sdw5-2 " 42183 "
8 " 6 " p " p " s " u " 48212 " sdw5 " sdw5-1 " 42182 "
16 " 6 " m " m " s " u " 58212 " sdw1 " sdw1-2 " 52820 "
3 " 1 " p " p " s " u " 48213 " sdw1 " sdw1-2 " 42183 "
11 " 1 " m " m " s " u " 58213 " sdw3 " sdw3-1 " 52821 "
(17 rows) (原文地址:https://discuss.pivotal.io/hc/en-us/articles/202646953-What-are-mode-and-status-columns-under-gp-segment-configuration-table)
[转]What are mode and status columns under gp_segment_configuration table的更多相关文章
- 1503 - A PRIMARY KEY must include all columns in the table's partitioning function
1503 - A PRIMARY KEY must include all columns in the table's partitioning function 错误的原因:表的主键字段必须包含分 ...
- 分区实践 A PRIMARY KEY must include all columns in the table's partitioning function
MySQL :: MySQL 8.0 Reference Manual :: 23 Partitioning https://dev.mysql.com/doc/refman/8.0/en/parti ...
- mysqladmin processlist; show processlist/status/open tables/engine/variables/table status/columns/grants/index/privileges/innodb status/logs/warnings/////; 结果筛选
mysqladmin showprocesslist可查看完整sql需要权限. SHOW PROCESSLIST显示哪些线程正在运行.您也可以使用mysqladmin processlist语句得到此 ...
- Specify Computed Columns in a Table
https://docs.microsoft.com/en-us/sql/relational-databases/tables/specify-computed-columns-in-a-table ...
- How to get the mapping relationship between two columns in a table
If a table have column A and B Count(distinct A) as Da Count(distinct B) as Db Count(distinct A, B) ...
- flask启动常见问题1:sqlalchemy.exc.ArgumentError: Mapper mapped class UserCode->data_system_user_email could not assemble any primary key columns for mapped table 'data_system_user_email'
我的描述:当我编辑好flask以后,ORM映射数据库完成,启动项目时,发生现象: 解决: 看字面的意思是主键导致的错误,于是我查看了data_system_user_email的键参数配置,发现表没有 ...
- return columns.All(new Func<string, bool>(list.Contains));
internal static bool VerifyColumns(SqlConnection conn, string table, params string[] columns) ...
- db2 Hidden columns
When a table column is defined with the implicitly hidden attribute, that column is unavailable unle ...
- Mysql --分区表(5)Columns分区
COLUMNS分区 COLUMNS分区是RANGE和LIST分区的变种.COLUMNS分区支持多列作为分区键进行分区 RANGE COLUNMS分区和LIST COLUMNS都支持非INT型列作为分区 ...
随机推荐
- 电脑的fn锁，f1-f12与功能键 互换
提要: 有些机子特别逆天,比如说Thinkpad e系列.好好的f1-f12一定要加上fn才能按出来,默认的是画在上面的功能键,作为娱乐来说其实是还不错的,但是像我等程序员就觉得特别逆天了.你有两个选 ...
- 微信小程序 - tabbar动态更换图标以及文字
大家不喜欢小程序的tabbar原因之一就是它太死板,tabbar一旦在app.json定义以后文字不能改,图标不能改! 我要自制tabbar!!! 其实在微信更新完1.9.0基础调试以后就推出了更新方 ...
- Python在线dlib库地址
一.地址 https://pypi.python.org/pypi/dlib/18.17.100
- 定时执行任务FluentScheduler
private void Form1_Load(object sender, EventArgs e) { Registry registry = new Registry(); registry.S ...
- Java 判断Windows下某个进程是否运行
public static void main(String[] args) { String keyWord = "chrome.exe"; Runtime runtime = ...
- Mybatis-Generator自动生成XML文件以及接口和实体类
整合了MySQL和Oracle配置文件生成方法 这个是整个文件夹的下载地址:http://www.codepeople.cn/download 主要给大家介绍一下generatorConfig.xml ...
- Python2.7.14新手学习
python2.7.14 让用户选择一个功能,然后对其进行操作的例子.中间有问题的是年龄没有做是否是数字判断 注意:和版本python3不同的地方 1.编码 2.输入地方是raw_input 3.业务 ...
- unique_ptr与std::move的使用
形参为unique_ptr u2,而后实参为std::move(unique_ptr u1),这样会将原本u1的内存传递给u2,避免了传递拷贝.例如: void fun(std::unique_ptr ...
- 基于Echarts的股票K线图展示
发布时间:2018-10-31 技术:javascript+html5+canvas 概述 基于echarts的股票K线图展示,只需引用单个插件,通过简单配置,导入数据,即可实现炫酷复杂的K线 ...
- maven 下载 源码和javadoc命令(转)
转自:http://blog.csdn.net/topwqp/article/details/8902863 maven 下载 源码和javadoc命令 目录(?)[+] Maven命令下载源码和ja ...