Hello Experts,
We've been having a strange problem with one of our databases.
A summary of the setup follows:
- We are running postgresql 9.6.9 on Centos 7.
- We are using postgresql native streaming replication
- There is one master and one hot standby
- The master is archiving it's WAL fi
Le ven. 14 déc. 2018 à 07:00, Ron a écrit :
> On 12/13/2018 08:25 PM, Rene Romero Benavides wrote:
> > This topic seems to be always open to discussion. In my opinion, it
> > depends on how big your work dataset is, there's no use in sizing
> > shared_buffers beyond that size. I think, the most r
On 12/13/2018 08:25 PM, Rene Romero Benavides wrote:
This topic seems to be always open to discussion. In my opinion, it
depends on how big your work dataset is, there's no use in sizing
shared_buffers beyond that size. I think, the most reasonable thing is
analyzing each case as proposed here:
On Fri, Dec 14, 2018 at 2:17 AM Ron wrote:
> https://www.postgresql.org/docs/9.6/runtime-config-resource.html
>
> The docs say, "If you have a dedicated database server with 1GB or more of
> RAM, a reasonable starting value for shared_buffers is 25%".
>
> But that's pretty archaic in 2018. What i
This topic seems to be always open to discussion. In my opinion, it depends
on how big your work dataset is, there's no use in sizing shared_buffers
beyond that size. I think, the most reasonable thing is analyzing each case
as proposed here:
https://www.keithf4.com/a-large-database-does-not-mean-l
> From: Tony Shelver
> Just a side comment: Why use phpPgAdmin when pgAdmin 4.6 is current, free and
> readily available?
> It also has a graphical table-from-file loader as well.
I can’t speak for the original poster, but there are multiple reasons that
might be:
* You came from the mysql wor
Hi,
https://www.postgresql.org/docs/9.6/runtime-config-resource.html
The docs say, "If you have a dedicated database server with 1GB or more of
RAM, a reasonable starting value for shared_buffers is 25%".
But that's pretty archaic in 2018. What if the dedicated database server
has 128GB RAM
On 12/13/18 4:23 AM, hvjunk wrote:
Good day,
I’m running into a problem with pg_top inside a LXC container (unprivileged
on ProxMox).
1) Seems the pgtop “foundry” directory isn’t working?
http://ptop.projects.pgfoundry.org/
Might want to try:
https://github.com/markwkm/pg_top
Forbidde
Good day,
I’m running into a problem with pg_top inside a LXC container (unprivileged on
ProxMox).
1) Seems the pgtop “foundry” directory isn’t working?
http://ptop.projects.pgfoundry.org/
Forbidden
You don't have permission to access / on this server.
2) The error is a segmentation fault, l
Thank you very much.
It worked.
Regards
Johann
On Thu, 13 Dec 2018 at 11:03, Andrew Gierth wrote:
>
> > "Johann" == Johann Spies writes:
>
> Johann> How can I transform the following definition to index pubyear
> Johann> as integer and not text?
>
> Johann> CREATE INDEX pubyear_idx
> Jo
> "Johann" == Johann Spies writes:
Johann> How can I transform the following definition to index pubyear
Johann> as integer and not text?
Johann> CREATE INDEX pubyear_idx
Johann> ON some_table_where_data_field_is_of_type_jsonb USING btree
Johann> ((data -> 'REC'::text) -> 's
On 12/12/18 3:45 μ.μ., Chris Withers wrote:
On 11/12/2018 14:48, Achilleas Mantzios wrote:
On 11/12/18 4:00 μ.μ., Chris Withers wrote:
I'm looking after a multi-tenant PG 9.4 cluster, and we've started getting
alerts for the number of WALs on the server.
It'd be great to understand what's gen
On Thu, 6 Dec 2018 at 19:27, Laurenz Albe wrote:
>
> Replace
>
> COLLATE pg_catalog."default"
>
> with
>
> ::integer
which results in
syntax error at or near "::"
LINE 2: ...'::text) -> 'pub_info'::text) ->> '@pubyear'::text)::integer
moving the ::integer into the bracket also:
syntax erro
13 matches
Mail list logo
