Jevon Cowell wrote:
> What I'm seeing is that for the same query *and* query id,
> there are two rows with different statistics data *at the same time*. For
> example one row can have 2 calls while another can have 4
That looks normal. The unicity to expect is on
(queryid, userid, dbid,
On 16/05/25 21:33, Achilleas Mantzios wrote:
On 16/5/25 18:45, Moreno Andreo wrote:
Hi,
we are moving our old binary data approach, moving them from
bytea fields in a table to external storage (making database smaller
and related operations faster and smarter).
In short, we have a job t
On 5/19/25 09:14, Moreno Andreo wrote:
On 16/05/25 21:33, Achilleas Mantzios wrote:
On 16/5/25 18:45, Moreno Andreo wrote:
Hi,
we are moving our old binary data approach, moving them from
bytea fields in a table to external storage (making database smaller
and related operations faster
On 19/05/25 14:41, Achilleas Mantzios wrote:
On 5/19/25 09:14, Moreno Andreo wrote:
On 16/05/25 21:33, Achilleas Mantzios wrote:
On 16/5/25 18:45, Moreno Andreo wrote:
Hi,
we are moving our old binary data approach, moving them from
bytea fields in a table to external storage (makin
Hello all,
Could i get a help, postgres 1 billion records indexed table, search speed
in a normal machine, no parallel processing ... for a knowledge ??
regards,
Dias Thomas
On Monday, May 19, 2025, Dias Thomas wrote:
> Hello all,
> Could i get a help, postgres 1 billion records indexed table, search
> speed in a normal machine, no parallel processing ... for a knowledge ??
>
https://wiki.postgresql.org/wiki/Slow_Query_Questions
David J.
On Mon, May 19, 2025 at 12:12 PM Dias Thomas wrote:
> Hello all,
> Could i get a help, postgres 1 billion records indexed table, search
> speed in a normal machine, no parallel processing ... for a knowledge ??
>
1. How big are the records?
2. How big are the keys?
3. What is a normal machine?
Spinning rust? SSD? NVMe? SATA? SCSI? Fiber?
Anyway... off the cuff, for 1 giga-rows, that's about a 50GB table. Small
enough that you can easily test that yourself.
On Mon, May 19, 2025 at 12:38 PM Dias Thomas wrote:
> Hello,
> 1 field 20 chars plus primary key id field - small table
> ind
On 19/5/25 17:38, Moreno Andreo wrote:
On 19/05/25 14:41, Achilleas Mantzios wrote:
On 5/19/25 09:14, Moreno Andreo wrote:
On 16/05/25 21:33, Achilleas Mantzios wrote:
On 16/5/25 18:45, Moreno Andreo wrote:
Hi,
we are moving our old binary data approach, moving them from
bytea fie
Ok?
Honestly, your questions puzzle me: PG is open source, binaries are
available for Windows, every Linux distro, and even BSD. And *the database
is pretty small*.
Install it, and *test it yourself*.
Then you'll have the answer.
On Mon, May 19, 2025 at 12:57 PM Dias Thomas wrote:
> Hi,
> I
On Mon, May 19, 2025 at 09:07:35AM +0200, Daniel Verite wrote:
> That looks normal. The unicity to expect is on
> (queryid, userid, dbid, toplevel).
>
> From https://www.postgresql.org/docs/current/pgstatstatements.html :
>
> This view contains one row for each distinct combination of database
11 matches
Mail list logo
