MENU
Select one incorrect description about changing the settings of PostgreSQL during operation.
Suggested Answer: A, C
Get Premium PGCES-02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
37 comments · newest first
KI
Kiley
10 months ago
E is true, some parameters can't be changed on the fly with SET.
GE
Geoffrey
11 months ago
C is misleading, SET values do override postgresql.conf for the session only.
AL
Alisha
11 months ago
Wait, are you saying superuser SET values don't carry over? That sounds off.
LA
Lamonica
11 months ago
Totally agree, SHOW ALL is super handy for checking settings!
MA
Marquetta
11 months ago
A is correct, you can use SHOW to check parameter values.
DA
Danica
12 months ago
I vaguely recall that some parameters can't be changed with SET, but I can't remember which ones.
CH
Cheryl
12 months ago
I think I practiced a similar question where we discussed the priority of SET versus postgresql.conf, and I believe SET has higher priority.
ST
Stanford
12 months ago
I'm a bit unsure about option D; I thought SET changes only apply to the current session, not future connections.
HA
Hannah
1 year ago
I remember that the SHOW command is definitely used to check parameter values, so that one seems correct.
CO
Colette
1 year ago
I've worked with PostgreSQL configuration before, so I think I've got a good handle on this. I'll just double-check my understanding quickly.
BA
Barrie
1 year ago
The wording on these options is tricky. I'll need to read them carefully and make sure I understand the nuances.
AL
Alpha
1 year ago
Okay, let me think this through. I know there are some parameters that can only be set in the config file, not at runtime. I'll need to remember that.
LI
Ligia
1 year ago
Hmm, I'm a bit unsure about the differences between the SHOW and SET commands. I'll need to review those details.
LE
Lelia
1 year ago
This looks like a straightforward PostgreSQL configuration question. I'm pretty confident I can handle this one.
KA
Kara
1 year ago
Hmm, I'm not too familiar with the Cisco Unified JTAPI implementation. I'll have to try to recall what I know about the different types of endpoints it supports.
FE
Fernanda
1 year ago
The key here is that the technology is new and there's uncertainty about its longevity and reliability. I think the risk register is the way to go to document and manage those risks.
BU
Buffy
1 year ago
Ugh, I'm really struggling with this one. Virtualization is such a complex topic, and I'm not sure I fully grasp all the security implications. I'll have to guess and hope for the best.
CA
Cassandra
1 year ago
A superuser with the power to change settings? I bet they're the ones who decide when to restart the database for 'maintenance'.
GA
Gail
1 year ago
D) Values set by a superuser using the SET command are valid for different connections made later.
KI
Kizzy
1 year ago
C) Changes that can be made using the SET command have higher priority than ones in postgresql.conf.
AS
Asuncion
1 year ago
B) All of the current settings can be displayed using the SHOW ALL command.
BE
Bettye
1 year ago
A) The current value of a parameter can be confirmed using the SHOW command.
PE
Pete
1 year ago
Hmm, so the superuser settings don't stick around for other connections? That's a bit disappointing, but I guess it makes sense.
ED
Eden
1 year ago
C) Changes that can be made using the SET command have higher priority than ones in postgresql.conf.
MA
Maybelle
1 year ago
B) All of the current settings can be displayed using the SHOW ALL command.
NI
Nieves
1 year ago
A) The current value of a parameter can be confirmed using the SHOW command.
VI
Vincenza
1 year ago
Aha, good to know there are some parameters that can't be set with the SET command. Gotta keep an eye on those.
RE
Remona
1 year ago
Lonny: Definitely, we need to make sure we are monitoring all the settings closely.
LO
Lonny
1 year ago
User 2: Absolutely, those parameters could have a big impact on the operation of PostgreSQL.
MO
Moon
1 year ago
User 1: Yes, it's important to be aware of the parameters that can't be set with the SET command.
WI
Wilbert
1 year ago
Wait, so the SET command overrides the postgresql.conf file? That seems a bit too powerful if you ask me.
SI
Simona
1 year ago
That SHOW ALL command sounds pretty useful! I bet it would give me a comprehensive overview of all the settings.
TA
Tamala
1 year ago
User 2: I agree, it's a great way to see everything at once.
KI
Kimberlie
1 year ago
User 1: Yeah, the SHOW ALL command is really handy for getting a full view of all the settings.
GE
Georgiann
2 years ago
I believe option D is incorrect because changes made using the SET command are only temporary and do not persist for future connections.
JA
Jamika
2 years ago
I agree with Novella. The SET command values are only valid for the current session, not for later connections.
NO
Novella
2 years ago
I think the incorrect description is D) Values set by a superuser using the SET command are valid for different connections made later.