Re: Column type modification in big tables

[Dominique Devienne]

On Tue, Aug 13, 2024 at 10:54 PM Peter J. Holzer  wrote:
> You could look at the data files. Tables in PostgreSQL are stored as a
> series of 1GB files, so you watching them being created and/or read
> gives you a pretty good idea about progress.

Thanks Peter, very insightful. Appreciated. --DD

Using PQsocketPoll() for PIPELINE mode

[Dominique Devienne]

Hi. I've now used successfully the new PQsocketPoll() API
in the context of waiting for notifications, using beta2 and 3.

But now I'm looking into using it in the context of PIPELINE mode.
Where I suppose both forRead and forWrite are 1, but the return
code only indicates whether the condition is met. The doc says nothing
about OR or AND semantic, when both forRead and forWrite are true.

Perhaps it's deemed obvious from the use of select() or poll()?
Or is one supposed to call it once with forRead=forWrite=1 and
a timeout, then call it again twice with just one forFlag set and
a 0 timeout, to know the "details" about which "side" is ready?

Or hasn't this use case been considered for PQsocketPoll(),
and thus the current return code isn't has precise as it could be?

Thanks for any precisions, --DD

What is the best way to upgrade pgAdmin on Windows?

[毛毛]

Hey there,

I just found out my pgAdmin is version 7.6, while the current version is 8.6. 
Looks like it's time for an upgrade!

The notification I got had a link to the EDB site with a bunch of PostgreSQL 
installers listed. Thing is, I don't want to mess up my database. So I figured 
it'd be smart to learn some best practices for upgrading before I dive in.

Any tips or advice on how to do this safely? Thanks in advance!