Postgres Pro
Downloads
Home   >   mailing lists

Re: [GENERAL] huge table occupation after updates - Mailing list pgsql-general

From David G. Johnston
Subject Re: [GENERAL] huge table occupation after updates
Date
Msg-id CAKFQuwY-Vzo_DjA+m1EzXGXkKmffSt3Db+-D=rgYaJJpkqnhgw@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] huge table occupation after updates  (Tom DalPozzo <t.dalpozzo@gmail.com>)
Responses Re: [GENERAL] huge table occupation after updates
List pgsql-general
Tree view
On Saturday, December 10, 2016, Tom DalPozzo <t.dalpozzo@gmail.com> wrote:

​I have one direct DB client (let's name it MIDAPP) only. This client of the DB is a server for up to 10000 final clients.
Any time MIDAPP is going to reply to a client, it must save a "status record with some data" related to that client and only after that, answering /committing the final client.
The next time the same final client will ask something, the same status record will be updated again (with a different content).

Why do you want to pay for concurrency control when you don't seem to need it?  While PostgreSQL likely can do what you need I suspect there are applications out there that can solve this specific problem better.  Even something as simple as a flat file, one per "final client", written atomically and fsynced after each write/rename.

David J,

pgsql-general by date:

Previous
From: Patrick B
Date:
Subject: Re: [GENERAL] WAL history files - Pgsql 9.2
Next
From: Michael Paquier
Date:
Subject: Re: [GENERAL] Re: [ADMIN] Would like to below scenario is possiblefor getting page/block corruption