On Thu, Apr 6, 2023 at 11:13 PM Tatsuo Ishii wrote:
> I am welcome you to
> join and continue the discussion on pgpool mailing list.
I truly believe that this problem – HA – is PostgreSQL's, not 3rd
party's. And it's a shame that Postgres itself doesn't solve this. So
we're discussing it here.
> Communication takes time – network latencies. What if during this
> communication, the situation becomes different?
We have to accept it (and do the best to mitigate any consequence of
the problem). I think there's no such a system which presuppose 0
communication latency.
> What if some of the
On Thu, Apr 6, 2023 at 9:17 PM Tatsuo Ishii wrote:
> With quorum failover is enabled, w0, w1, and w2 communicate each other
> to vote who is correct (if it cannot communicate, it regards other
> watchdog is down). In the case above w0 and w1 are majority and will
> win.
Communication takes time –
On 4/6/23 23:16, Tatsuo Ishii wrote:
But, I heard PgPool is still affected by Split brain syndrome.
Can you elaborate more? If more than 3 pgpool watchdog nodes (the
number of nodes must be odd) are configured, a split brain can be
avoided.
Split brain is a hard situation to avoid. I suppose OP
>> > But, I heard PgPool is still affected by Split brain syndrome.
>>
>> Can you elaborate more? If more than 3 pgpool watchdog nodes (the
>> number of nodes must be odd) are configured, a split brain can be
>> avoided.
>
> Split brain is a hard situation to avoid. I suppose OP is talking abou
Looking at the result of:
pg_dump --help
Usage:
pg_dump [OPTION]... [DBNAME]
... -n, --schema=PATTERN dump the specified schema(s) only...
-s, --schema-only dump only the schema, no data...
So: pg_dump -s -n
It works for me...
Cheers
Brent Wood
On Friday, Apri
Atul Kumar writes:
> Please help me in telling that how I can take the backup of one single
> schema without its data using pg_dump utility ?
Doesn't "pg_dump -s -n ..." do what you want?
regards, tom lane
>From the man page….
“
-s
--schema-only
Dump only the object definitions (schema), not data.
…..”
On Thu, Apr 6, 2023 at 18:40 Atul Kumar wrote:
> Hi,
>
> Please help me in telling that how I can take the backup of one single
> schema without its data using pg_dump utility ?
>
>
> So far, I
Hi,
Please help me in telling that how I can take the backup of one single
schema without its data using pg_dump utility ?
So far, I could not find anything suitable for doing so.
Regards,
Atul
Greetings,
* Imre Samu (pella.s...@gmail.com) wrote:
> Theory: Maybe the search doesn't always work ...
It does ... but perhaps not as expected (or as ideal).
> Is this a known problem?
Yes and no.
> My use case:
> in https://www.postgresql.org/list/ -> "Search the Archives"
> search for the
That is the answer. Postgresql can upsert easily via triggers and on
conflict.
Thanks,
Ben
On Thu, Apr 6, 2023, 5:01 PM Adrian Klaver
wrote:
> On 4/5/23 23:21, Louis Tian wrote:
> > This is a question/feature request.
> >
>
> > Given the definition of upsert, I'd expect an upsert command to do
On 4/5/23 23:21, Louis Tian wrote:
This is a question/feature request.
Given the definition of upsert, I'd expect an upsert command to do the
following.
- `upsert into person (id, name) values (0, 'foo')` to insert a new row
- `upsert into person (id, is_active) values (0, true)` updates the
On Thu, Apr 6, 2023 at 1:21 PM Louis Tian wrote:
> An implicit assumption behind this definition is that table must have a
> primary key for the upsert operation to make sense since it's the primary key
> that uniquely identifies a row.
It could just be a unique index or a unique constraint. So
This is a question/feature request.
Virtually all references on the internet today suggests one can "upsert" in
PostgreSQL using the "insert ... on conflict do update ..." statement.
But this is not complete true.
The PostgreSQL's own wiki page
(https://wiki.postgresql.org/wiki/UPSERT#.22UPS
Hi,
Theory: Maybe the search doesn't always work ...
Is this a known problem?
My use case:
in https://www.postgresql.org/list/ -> "Search the Archives"
search for the "large database backup"
->
https://www.postgresql.org/search/?m=1&q=large+database+backup&l=&d=365&s=r
-> "Your search for large
Our PostgreSQL 15.2 instance running on Ubuntu 18.04 has crashed with
this error:
2023-04-05 09:24:03.448 UTC [15227] ERROR: index "pg_class_oid_index"
contains unexpected zero page at block 0
2023-04-05 09:24:03.448 UTC [15227] HINT: Please REINDEX it.
...
2023-04-05 13:05:25.018 UTC [15437]
ro
On Wed, 05 Apr 2023 16:50:15 +0900 (JST)
Tatsuo Ishii wrote:
> > But, I heard PgPool is still affected by Split brain syndrome.
>
> Can you elaborate more? If more than 3 pgpool watchdog nodes (the
> number of nodes must be odd) are configured, a split brain can be
> avoided.
Split brain is a
Greetings,
Please don't top-post on the PG mailing lists, it makes it harder to
follow the discussion.
* Marco Fortina (marco_fort...@hotmail.it) wrote:
> https://commitfest.postgresql.org/42/3867/ is not exacly what I proposed as
> new feature to developers.
I understood what you were proposin
Thanks Stephen.
https://commitfest.postgresql.org/42/3867/ is not exacly what I proposed as new
feature to developers.
If I'm not wrong, almost all main memory areas have a fixed size:
shared_buffers
effective_cache_size
wal_buffers
Instead, work_mem is per-process dynamically allocated up to
Thanks Stephen.
https://commitfest.postgresql.org/42/3867/ is not exacly what I proposed as new
feature to developers.
If I'm not wrong, almost all main memory areas have a fixed size:
shared_buffers
effective_cache_size
wal_buffers
Instead, work_mem is per-process dynamically allocated up to
Greetings,
* Marco Fortina (marco_fort...@hotmail.it) wrote:
> I would like to propose to developers a new feature to replace the private
> management of the work mem with a management through shared memory: allocated
> at the start of PostgreSQL this area should be shared to all worker processe
Hello there!
I would like to propose to developers a new feature to replace the private
management of the work mem with a management through shared memory: allocated
at the start of PostgreSQL this area should be shared to all worker processes
as for example Oracle Database PGA do.
This would
22 matches
Mail list logo
