On Mon, Aug 24, 2020 at 12:01:00PM -0400, Bruce Momjian wrote:
> Sure, I can wait. Is this the only place where it would make sense?
I think so. If there are other places, it does not prevent improving
what we already know needs improvement.
FWIW, the layout I was thinking about is something li
Yes, I did.
On Mon, Aug 24, 2020 at 10:43 PM Fujii Masao
wrote:
>
>
> On 2020/08/25 11:22, Michael Paquier wrote:
> > On Mon, Aug 24, 2020 at 03:56:43PM -0400, rams nalabolu wrote:
> >> I did the following steps to perform switchover
> >> 1) ran a checkpoint on primary.
> >> 2) verified secondar
On 2020/08/25 11:22, Michael Paquier wrote:
On Mon, Aug 24, 2020 at 03:56:43PM -0400, rams nalabolu wrote:
I did the following steps to perform switchover
1) ran a checkpoint on primary.
2) verified secondary status and it is up to date with primary.
3) stopped primary using pg_ctl -mf i.e fo
On Mon, Aug 24, 2020 at 03:56:43PM -0400, rams nalabolu wrote:
> I did the following steps to perform switchover
> 1) ran a checkpoint on primary.
> 2) verified secondary status and it is up to date with primary.
> 3) stopped primary using pg_ctl -mf i.e force.
This is not a force mode, but the fa
On Tue, Aug 25, 2020 at 06:21:28AM +0530, mahammad shoyab wrote:
> Hi please release me from this group
It is possible to manage your subscriptions to the PostgreSQL
community mailing lists using your community account. Please see
here:
https://lists.postgresql.org/manage/
--
Michael
signature.
Hi please release me from this group
On Mon, Aug 24, 2020 at 04:00:09PM -0400, Stephen Frost wrote:
> Greetings,
>
> * Bruce Momjian (br...@momjian.us) wrote:
> > A few years ago I figured out how to create intermediate certificates
> > that are transferred across OpenSSL connections by using the v3_ca
> > extension, and added this t
Greetings,
* Bruce Momjian (br...@momjian.us) wrote:
> A few years ago I figured out how to create intermediate certificates
> that are transferred across OpenSSL connections by using the v3_ca
> extension, and added this to the PG documentation.
>
> I have now just figured out that v3_ca is just
Hi All,
I'm trying to do the Switchover process in postgres.
1) I have my primary cluster running on port 5432 on server A
2) secondary cluster on the port 5432 on server B
I did setup streaming replication b/w primary and secondary using
replication slots.
I did the following steps to perform s
A few years ago I figured out how to create intermediate certificates
that are transferred across OpenSSL connections by using the v3_ca
extension, and added this to the PG documentation.
I have now just figured out that v3_ca is just a heading in the openssl
configuration file, e.g., /etc/ssl/ope
On Mon, Aug 24, 2020 at 9:09 AM Pavel Stehule
wrote:
>
>
> po 24. 8. 2020 v 18:00 odesílatel Bruce Momjian napsal:
>
>> On Mon, Aug 24, 2020 at 05:51:29PM +0200, Pavel Stehule wrote:
>> > sure. Maybe enhancing about sentence like "it is not possible in a
>> function."
>> >
>> > and
>> >
>> > "a
po 24. 8. 2020 v 18:00 odesílatel Bruce Momjian napsal:
> On Mon, Aug 24, 2020 at 05:51:29PM +0200, Pavel Stehule wrote:
> > sure. Maybe enhancing about sentence like "it is not possible in a
> function."
> >
> > and
> >
> > "a procedure can commit (or rollback) and begin new transactions during
On Mon, Aug 24, 2020 at 11:59:22AM -0400, Alvaro Herrera wrote:
> On 2020-Aug-24, Bruce Momjian wrote:
>
> > I don't think it is worth it, plus we would need to adjust the docs if
> > system catalog layout changes. I think we just want something concise
> > and simple, but also accurate.
>
> I a
On Mon, Aug 24, 2020 at 05:51:29PM +0200, Pavel Stehule wrote:
> sure. Maybe enhancing about sentence like "it is not possible in a function."
>
> and
>
> "a procedure can commit (or rollback) and begin new transactions during its
> execution"
OK, updated patch.
--
Bruce Momjian
On 2020-Aug-24, Bruce Momjian wrote:
> I don't think it is worth it, plus we would need to adjust the docs if
> system catalog layout changes. I think we just want something concise
> and simple, but also accurate.
I argued for \dAo, not straight catalog output -- that was a straw man.
I can't
po 24. 8. 2020 v 17:38 odesílatel Bruce Momjian napsal:
> On Mon, Aug 24, 2020 at 11:35:57AM -0400, Bruce Momjian wrote:
> > On Mon, Aug 24, 2020 at 05:24:19PM +0200, Pavel Stehule wrote:
> > >
> > >
> > > po 24. 8. 2020 v 17:01 odesílatel Bruce Momjian
> napsal:
> > >
> > > On Sat, Aug 22,
On Mon, Aug 24, 2020 at 11:35:57AM -0400, Bruce Momjian wrote:
> On Mon, Aug 24, 2020 at 05:24:19PM +0200, Pavel Stehule wrote:
> >
> >
> > po 24. 8. 2020 v 17:01 odesílatel Bruce Momjian napsal:
> >
> > On Sat, Aug 22, 2020 at 01:21:43PM -0700, David G. Johnston wrote:
> > > On Sat, Au
> 24 авг. 2020 г., в 18:07, Bruce Momjian написал(а):
>
> On Mon, Aug 24, 2020 at 07:40:49AM -0700, David G. Johnston wrote:
>> On Mon, Aug 24, 2020 at 6:17 AM Олег Самойлов wrote:
>>
>>There must not be constraints at all. Constraints are needed to check
>>incoming data to the table
On Mon, Aug 24, 2020 at 05:24:19PM +0200, Pavel Stehule wrote:
>
>
> po 24. 8. 2020 v 17:01 odesílatel Bruce Momjian napsal:
>
> On Sat, Aug 22, 2020 at 01:21:43PM -0700, David G. Johnston wrote:
> > On Sat, Aug 22, 2020 at 10:14 AM Bruce Momjian wrote:
> >
> > On Fri, Aug
po 24. 8. 2020 v 17:01 odesílatel Bruce Momjian napsal:
> On Sat, Aug 22, 2020 at 01:21:43PM -0700, David G. Johnston wrote:
> > On Sat, Aug 22, 2020 at 10:14 AM Bruce Momjian wrote:
> >
> > On Fri, Aug 21, 2020 at 07:42:35PM -0700, David G. Johnston wrote:
> >
> > > [...] the CALL comma
On Mon, Aug 24, 2020 at 07:40:49AM -0700, David G. Johnston wrote:
> On Mon, Aug 24, 2020 at 6:17 AM Олег Самойлов wrote:
>
> There must not be constraints at all. Constraints are needed to check
> incoming data to the table. But here table is read-only for database!
>
>
> Please don't
On Sat, Aug 22, 2020 at 01:21:43PM -0700, David G. Johnston wrote:
> On Sat, Aug 22, 2020 at 10:14 AM Bruce Momjian wrote:
>
> On Fri, Aug 21, 2020 at 07:42:35PM -0700, David G. Johnston wrote:
>
> > [...] the CALL command. If the CALL command is not part of an explicit
> > transact
On Mon, Aug 24, 2020 at 6:17 AM Олег Самойлов wrote:
> There must not be constraints at all. Constraints are needed to check
> incoming data to the table. But here table is read-only for database!
>
Please don't top-post.
> So all your constraints is totally useless.
> > > could become:
> > >
On Sat, Aug 22, 2020 at 02:59:02PM -0400, Alvaro Herrera wrote:
> On 2020-Aug-22, Tom Lane wrote:
>
> > If you don't want to go all the way and list the operators with their
> > input types, maybe we should just do what the OP thought was correct
> > and delete the duplicate operator names. It's
There must not be constraints at all. Constraints are needed to check incoming
data to the table. But here table is read-only for database!
So all your constraints is totally useless.
> > could become:
> >
> > connection_from text check(connection_from ~ '^[^:]+:[0-9]+$) -- the host
> > and
> >
On Sun, Aug 23, 2020 at 09:11:58PM +0900, Michael Paquier wrote:
> I have looked again at the documentation and found just the five
> places mentioned previously, giving the attached.
And fixed with 77c1537, so we are done here.
--
Michael
signature.asc
Description: PGP signature
26 matches
Mail list logo
