| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, David Christensen <david(dot)christensen(at)crunchydata(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: Initdb-time block size specification |
| Date: | 2023-06-30 23:16:18 |
| Message-ID: | ZJ9iQulqbPeTqi57@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 30, 2023 at 04:04:57PM -0700, Andres Freund wrote:
> Hi,
>
> On 2023-06-30 18:58:20 -0400, Bruce Momjian wrote:
> > > [1] On linux I think you need to use stat() to figure out the st_dev for a
> > > file, then look in /proc/self/mountinfo for the block device, use the name
> > > of the file to look in /sys/block/$d/queue/physical_block_size.
> >
> > I just got a new server:
> >
> > https://momjian.us/main/blogs/blog/2023.html#June_28_2023
> >
> > so tested this on my new M.2 NVME storage device:
> >
> > $ /sys/block/nvme0n1/queue/physical_block_size
> > 262144
>
> Ah, I got the relevant filename wrong. I think it's logical_block_size, not
> physical one (that's the size of addressing). I didn't realize because the
> devices I looked at have the same...
That one reports 512 _bytes_ for me:
$ cat /sys/block/nvme0n1/queue/logical_block_size
512
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2023-06-30 23:18:34 | Re: Initdb-time block size specification |
| Previous Message | Tomas Vondra | 2023-06-30 23:13:31 | Re: Initdb-time block size specification |