On 2019-Jan-30, Mariel Cherkassky wrote:
> It seems that the version of the db is 9.6.10 :
>
> psql -U db -d db -c "select version()";
> Password for user db:
> version
> ---
> PostgreSQL 9.6.1
Hey,
As I said, I'm getting this error for all the objects in a specific db. I
cant even connect to the database, I immediatly getting this error.
The bug was fixed in 9.6.10 but the db version is 9.6.10 so how can it
happen ? The db was installed in that version from the first place and *no
upgrad
Hi Thomas,
it is a Production system and we don’t have permanent access to it.
Also to have an auto_explain feature always on, is not an option in production.
I will ask the customer to give us notice asap the error present itself to
connect immediately and try to get a query plan.
Regards
Fabio
Hey,
I'm using postgresql 9.6.11. I wanted to ask something about the functions
I mentioned in the title :
I created the next table :
postgres=# \d students;
Table "public. students "
Column | Type | Modifiers
--+-+---
id| integer |
name| text|
age| integ
Hi Tom
After much performance measuring of VPS I believe you are right in
your suspicion about locale.
The database is full of Laos characters (it is a government system in
Laos). When I tested on my VPS (en_US.UTF-8) I get the crazy slow
performance, whereas my laptop postgresql is C.UTF-8.
Mo
According to the doc [1],
pg_total_relation_size add toasted data *and* indexes to the mix.
Any index, unique constraint, or primary key on your table ?
[1]
https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-ADMIN-DBSIZE
Le mer. 30 janv. 2019 à 11:42, Mariel Cherkassky <
marie
On Wed, 30 Jan 2019 14:19:52 +0100
Tumasgiu Rossini wrote:
> According to the doc [1],
> pg_total_relation_size add toasted data *and* indexes to the mix.
*and* FSM *and* VM.
> Any index, unique constraint, or primary key on your table ?
>
> [1]
> https://www.postgresql.org/docs/current/functi
There aren't any constraint or indexes, just a regular table. I didn't see
the fsm and vm files in the base dir. Were they created immediately for
every table or after some updates/deletes ?
On Wed, Jan 30, 2019, 3:27 PM Jehan-Guillaume (ioguix) de Rorthais <
iog...@free.fr wrote:
> On Wed, 30 J
"Jehan-Guillaume (ioguix) de Rorthais" writes:
> On Wed, 30 Jan 2019 14:19:52 +0100
> Tumasgiu Rossini wrote:
>> According to the doc [1],
>> pg_total_relation_size add toasted data *and* indexes to the mix.
> *and* FSM *and* VM.
Yeah. In this particular case, the other page presumably belongs
On Wed, Jan 30, 2019 at 3:57 AM Bob Jolliffe wrote:
> (i) whether the sort order makes sense for the Laos names; and
> (ii) what the locale settings are on the production server where the
> problem was first reported.
>
> There will be some turnaround before I get this information. I am
> guessin
Hi,
According to https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server :
> effective_cache_size should be set to an estimate of how much memory is
> available for disk caching by the operating system and within the database
> itself, after taking into account what's used by the OS itse
On Thu, Jan 31, 2019 at 1:00 PM Nandakumar M wrote:
> This is particularly confusing because in this thread Tom Lane says
> the following
>
Missed to link the thread..
https://postgrespro.com/list/thread-id/1813920
Regards,
Nanda
12 matches
Mail list logo
