Discuss EnterpriseDB PostgreSQL-Essentials Exam Topic 3 Question 6

Which query displays the name and size of all databases in your cluster using a meaningful unit?

ASELECT datname, pg_database_size(datname) FROM pg_database;

BSELECT datname, pg_size_pretty(pg_database_size(datname)) AS size FROM pg_database;

CSELECT name, size FROM pg_database;

DSHOW DATABASE SIZE;

Suggested Answer: B

Get Premium PostgreSQL-Essentials Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

29 comments · newest first

An 6 months ago

I feel confident with B. It's precise and informative.

Elliot 6 months ago

B gives both name and size clearly.

Helaine 7 months ago

D is too vague. It doesn't show names.

Anna 7 months ago

Option A is okay, but not user-friendly.

Dorian 7 months ago

I think option B is the best choice. It uses pg_size_pretty.

Veta 8 months ago

I disagree, B is the only one that makes sense here.

Denae 8 months ago

Wait, SHOW DATABASE SIZE? Is that even a valid query?

Jestine 8 months ago

I think C is missing the right functions.

Maybelle 8 months ago

Option B is the way to go. Keeps things simple and readable.

Brandee 8 months ago

Haha, option D is just wishful thinking. Gotta love those candidates who try to guess the answer.

Willis 8 months ago

SHOW DATABASE SIZE? Really? That's not even a valid PostgreSQL command.

Princess 9 months ago

I like how option B gives the database name and size in a single query. Much easier than having to do the conversion manually.

Avery 9 months ago

I don't recall seeing SHOW DATABASE SIZE in our practice, so I doubt it's the right choice.

Nan 9 months ago

I feel like A could be close, but it doesn't format the size in a meaningful way like B does.

Bernardine 9 months ago

I'm not entirely sure, but I remember something about pg_database_size being used in similar questions.

Carlee 9 months ago

Okay, let me see here. I think option A might be the simplest approach, just getting the raw database size values. But B does sound like it would be more useful in the real world. I'll have to weigh the pros and cons.

Annita 9 months ago

Easy peasy! Option B is definitely the correct answer. It gives you the database names and sizes in a nice, human-readable format. Can't go wrong with that.

Nieves 10 months ago

Option B looks good, it uses the pg_size_pretty function to display the database size in a more readable format.

Susana 10 months ago

Definitely B, it formats the size nicely!

Lyndia 10 months ago

I think the answer might be B because it uses pg_size_pretty, which makes the size more readable.

Freida 10 months ago

Agreed! It makes the size readable.

Ming 10 months ago

A is close, but it doesn't pretty-print the size.

Merissa 11 months ago

Hmm, I'm a bit unsure about this one. I know we need to get the database names and sizes, but I'm not sure which function to use. I'll have to think this through carefully.

Frederick 11 months ago

I think option B is the way to go here. It uses the pg_size_pretty() function to display the database sizes in a more readable format.

Allene 5 months ago

↳ replying to Frederick

Good point, B really enhances readability!

Jestine 6 months ago

↳ replying to Frederick

Option D seems too simple. B gives more info.

Ilene 6 months ago

↳ replying to Frederick

I was leaning towards A, but B is more user-friendly.

Harrison 6 months ago

↳ replying to Frederick

Yeah, pg_size_pretty() makes it so much clearer!

Tesha 6 months ago

↳ replying to Frederick

I agree, option B is definitely the best choice.

EnterpriseDB PostgreSQL-Essentials Exam - Topic 3 Question 6 Discussion