>
> 3) "...compatible to Microsoft's M365." I who am not a Windows user,
> knew what the OP meant. And if you go here:
>
> https://en.wikipedia.org/wiki/Microsoft_365#As_%22Microsoft_365%22
>
> You will see:
>
> "On March 30, 2020, Microsoft announced that the consumer plans of
> Office 365 would b
Hello,
I have two very simple questions:
1) I have an account at postgresql.org, but a link to a 'forgot password' seems
to be missing on the login page. I have my password stored only on an old
Fedora 32 computer. To change the password
when logged in, you need to supply the old password. In s
Michael:
On Mon, 25 Jul 2022 at 12:01, Michael J. Baars
wrote:
> 2) I have three psql clients running, a version 12.6, a version 13.4 and a
> version 14.3. Until now a 'select * from table;' showed the output in 'less'
> or something alike and exited from 'less' when
> the output was complete.
On 7/25/22 00:36, Adrian Klaver wrote:
Suitable driver is just that a driver that will suit the needs of
working on Windows 10 with MS Office/Office/Microsoft 365.
Literally every ODBC driver on Windows fits this definition. That is the
purpose of ODBC: having a uniform set of calls for variou
On 7/25/22 03:01, Michael J. Baars wrote:
Hello,
I have two very simple questions:
1) I have an account at postgresql.org, but a link to a 'forgot password' seems
to be missing on the login page. I have my password stored only on an old
Fedora 32 computer. To change the password
when logged i
On Mon, 2022-07-25 at 07:55 -0700, Adrian Klaver wrote:
> On 7/25/22 03:01, Michael J. Baars wrote:
> > Hello,
> >
> > I have two very simple questions:
> >
> > 1) I have an account at postgresql.org, but a link to a 'forgot password'
> > seems to be missing on the login page. I have my password
On 7/25/22 09:03, Michael J. Baars wrote:
On Mon, 2022-07-25 at 07:55 -0700, Adrian Klaver wrote:
On 7/25/22 03:01, Michael J. Baars wrote:
Hello,
Are all the clients running on the same machine?
Nope, three out of four machines run psql. I have four identical machines.
Small ones. Beelin
On Mon, 2022-07-25 at 09:13 -0700, Adrian Klaver wrote:
> On 7/25/22 09:03, Michael J. Baars wrote:
> > On Mon, 2022-07-25 at 07:55 -0700, Adrian Klaver wrote:
> > > On 7/25/22 03:01, Michael J. Baars wrote:
> > > > Hello,
> > > Are all the clients running on the same machine?
> >
> > Nope, three
On 7/25/22 09:23, Michael J. Baars wrote:
On Mon, 2022-07-25 at 09:13 -0700, Adrian Klaver wrote:
On 7/25/22 09:03, Michael J. Baars wrote:
On Mon, 2022-07-25 at 07:55 -0700, Adrian Klaver wrote:
On 7/25/22 03:01, Michael J. Baars wrote:
Hello,
I thought I already told this before, but so
On Mon, 25 Jul 2022, 18:41 Adrian Klaver, wrote:
> On 7/25/22 09:23, Michael J. Baars wrote:
> > On Mon, 2022-07-25 at 09:13 -0700, Adrian Klaver wrote:
> >> On 7/25/22 09:03, Michael J. Baars wrote:
> >>> On Mon, 2022-07-25 at 07:55 -0700, Adrian Klaver wrote:
> On 7/25/22 03:01, Michael J.
On 7/25/22 9:55 AM, Michael J. Baars wrote:
So the issue is with Fedora not Postgres.
No, it's psql. Setting PAGER to "more -e" solved the problem l, but I
never had to before. There are no other variables affecting this
behavior, so it must be psql internal default piping command th
I copied my testcase at the end. It runs OK and produces the output that I
expect using PG Version 14.4. But using Version 11.9 (and earlier 11
sub-versions), it fails to compile with this error:
syntax error at or near "."
lhs[j].a := rhs[j].a;
^
If I comment out the "Ideal approach" loop
On Mon, Jul 25, 2022 at 10:34 AM Bryn Llewellyn wrote:
> I copied my testcase at the end. It runs OK and produces the output that I
> expect using PG Version 14.4. But using Version 11.9 (and earlier 11
> sub-versions), it fails to compile with this error:
>
> *syntax error at or near "."*
> *lhs
On 7/25/22 10:37 AM, Michael J. Baars wrote:
Reply to list also
Ccing list
Use 'man more', manual pages are your friend.
I did, I just picked the wrong version. Got an the manual for ancient
version of more.
"Normally, less doesn't quit until you type "q". You can make it
qui
> david.g.johns...@gmail.com wrote:
>
>> b...@yugabyte.com wrote:
>>
>> I copied my testcase at the end. It runs OK and produces the output that I
>> expect using PG Version 14.4. But using Version 11.9 (and earlier 11
>> sub-versions), it fails to compile with this error:
>>
>> syntax error a
On 2022-Jul-25, Michael J. Baars wrote:
> No, it's psql. Setting PAGER to "more -e" solved the problem l, but I never
> had to before. There are no other variables affecting this behavior, so it
> must be psql internal default piping command that has changed.
Perhaps the settings are in the envir
I have a primary and backup database running 12.10 and synced with
streaming replication. I have a simple table that is returning different
results for the same query in the primary vs backup database.
On the primary DB:
> select tag::bytea, * from sentinel where tag =
'quote_merge_locs_mnj_NSX_
On 7/25/22 15:36, Kelly Burkhart wrote:
I have a primary and backup database running 12.10 and synced with
streaming replication. I have a simple table that is returning
different results for the same query in the primary vs backup database.
On the primary DB:
> select tag::bytea, * from se
18 matches
Mail list logo
