byte rounds - Search results

Queries in PostgreSQL: 4. Index scan

round( (1 - frac_visible) * -- the fraction of the pages not in the visibility map current_setting('seq_page_cost')::real * pages + current_setting('cpu_tuple_cost')::real * tuples ) FROM ( SELECT relpages * 0.0630 AS pages, reltuples

Blog >> PostgreSQL

PostgreSQL 18: part 4 or CommitFest 2025-01

bytes, pg_size_pretty(round(write_bytes/writes)) bytes_per_op FROM pg_stat_io WHERE

Blog >> PostgreSQL

PostgreSQL 16: part 5 or CommitFest 2023-03

bytes)) size, round(SUM(write_time)) "time, ms" FROM pg_stat_io WHERE writes > 0 GROUP

Blog >> PostgreSQL

PostgreSQL 16: part 4 or CommitFest 2023-01

round(x::numeric,1) point, count(*) AS density FROM samples GROUP BY point ORDER BY point \g (format=unaligned tuples_only=on fieldsep='\t') | gnuplot -e "set term png; set output 'data.png'; plot

Blog >> PostgreSQL

WAL in PostgreSQL: 3. Checkpoint

rounds, but not depend on the far-off history). The computed number of buffers is multiplied by the bgwriter_lru_multiplier coefficient (but anyway will not be greater than bgwriter_lru_maxpages ). The default values

Blog >> PostgreSQL

Indexes in PostgreSQL — 10 (Bloom)

byte integer numbers, so the value of m can be safely rounded up to 16. When