Hi, first time poster.
I just ran into a rather messy problem when doing a schema migration with
logical replication. I'm not entirely sure what went wrong, why, or how to
prevent it in the future. The migration I ran was pretty simple (though
auto-generated by Django):
BEGIN;ALTER TABLE "search_
On 11/20/18 13:00, Tom Lane wrote:
> If the stored XIDs were 64 bits wide, we'd not have to bother with all
> of this mess ... but adding another 64 bits to tuple headers would be
> a painful space cost, not to mention the storage compatibility issues.
People keep saying that. But didn't someone c
On 2018-12-08 15:23:19 -0800, Rob Sargent wrote:
>
>
> > On Dec 8, 2018, at 3:12 PM, Andres Freund wrote:
> >
> > On 2018-12-08 12:06:23 -0800, Jeremy Schneider wrote:
> >> On RDS PostgreSQL, the default is 25% of your server memory. This seems
> >> to be pretty widely accepted as a good starti
> On Dec 8, 2018, at 3:12 PM, Andres Freund wrote:
>
> On 2018-12-08 12:06:23 -0800, Jeremy Schneider wrote:
>> On RDS PostgreSQL, the default is 25% of your server memory. This seems
>> to be pretty widely accepted as a good starting point on PostgreSQL.
>
> FWIW, I think it's widely cited,
On 2018-12-08 12:06:23 -0800, Jeremy Schneider wrote:
> On RDS PostgreSQL, the default is 25% of your server memory. This seems
> to be pretty widely accepted as a good starting point on PostgreSQL.
FWIW, I think it's widely cited, but also bad advice. 25% for a OLTP
workload on a 1TB machine wit
so 8. 12. 2018 v 20:04 odesílatel Square Bob napsal:
> All;
>
>
> My apologies if this is off topic.
>
>
> Our company is moving to Aurora, In the past I would take care not to
> allow postgresql to over-commit memory beyond the actual memory on the
> server, which meant I would add the buffer po
All;
My apologies if this is off topic.
Our company is moving to Aurora, In the past I would take care not to
allow postgresql to over-commit memory beyond the actual memory on the
server, which meant I would add the buffer pool + (work_mem *
max_connections) + (maintenance_work_mem * autov
Hi,
Is there a substantive difference between the two, or are they just
different interfaces to the same action?
--
Angular momentum makes the world go 'round.
In v9.2 (yes, I know it's EOL; there's nothing I can do about it), what
tables do I query to get these values, and can I also get them from the
streamed replication host?
Database cluster state
Latest checkpoint location
Time of latest checkpoint
[postgres@fpslbxhaprl05 ~]$ pg_controldata
p
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.
On Fri, 7 Dec 2018 at 23:35, Adrian Klaver
wrote:
> On 12/7/18 9:04 AM, s4...@yahoo.co.jp wrote:
> > I didn't specify any schema, so it was cr
10 matches
Mail list logo
