Tom Lane writes:
> ... but expression-index syntax has the restriction that you need
> parentheses around an expression unless it is, or at least looks like,
> a function call. CAST() looks enough like a function call for this
> purpose, v::t does not.
>
> I think there is relevant documentation
Re: Adam Brusselback 2017-11-11
> Hey Christoph, I tried starting it with init (service postgresql
> start), and pg_ctlcluster.
>
> I modified the pg_ctl.conf and set the timeout higher so I could just
> get my cluster back up and running properly, so I can't give you the
> info on what systemct
On 11/11/17 16:45, Jan Claeys wrote:
On Sat, 2017-11-11 at 14:23 +, Mark Morgan Lloyd wrote:
I think that the "preventing upgrades" route is the one to follow,
since inhibiting the restart would obviously present a risk that
something loaded dynamically could get out of step. As an at least
Hey Christoph, I tried starting it with init (service postgresql
start), and pg_ctlcluster.
I modified the pg_ctl.conf and set the timeout higher so I could just
get my cluster back up and running properly, so I can't give you the
info on what systemctl status says at the moment.
On Sat, Nov 11,
Lele Gaifax writes:
> while writing test cases for my SQL pretty printer tool[1], I found what seems
> a discrepancy in the "Type Casts" documentation[2]: it states that the two
> syntaxes are equivalent, but while
They are functionally equivalent ...
> EXCLUDE USING gist (CAST(company_id AS
On Sat, 2017-11-11 at 14:23 +, Mark Morgan Lloyd wrote:
> I think that the "preventing upgrades" route is the one to follow,
> since inhibiting the restart would obviously present a risk that
> something loaded dynamically could get out of step. As an at least
> temporary hack I've disabled una
On 11/11/17 13:45, Christoph Berg wrote:
Re: Magnus Hagander 2017-11-11
Is there any way that either the package maintainer or a site
administrator/programmer such as myself can mark the Postgres server
packages as "manual upgrade only" or similar? Or since I'm almost certainly
not the first p
When upgrading from https://download.postgresql.org/pub/repos/yum/10/fedora/
# dnf upgrade
...
Error: Package postgresql10-10.1-1PGDG.f25.x86_64.rpm is not signed
Regards, Clodoaldo
On Sat, Nov 11, 2017 at 2:23 PM, rob stone wrote:
>
>
> On Sat, 2017-11-11 at 13:03 +, Mark Morgan Lloyd wrote:
> > Apologies for something which is distro related, but I was bitten by
> > a
> > "silly mistake"- one of my own, I hasten to say- earlier.
> >
> > Several legacy programs written
Re: Magnus Hagander 2017-11-11
> > Is there any way that either the package maintainer or a site
> > administrator/programmer such as myself can mark the Postgres server
> > packages as "manual upgrade only" or similar? Or since I'm almost certainly
> > not the first person to be bitten by this,
Re: Tom Lane 2017-11-10 <8027.1510347...@sss.pgh.pa.us>
> > The recovery succeeds, but when I go to start the cluster on the
> > standby, it begins to replay the WAL, and does so for about 30
> > seconds. Then I get a line in my log saying:
>
> >> pg_ctl: server did not start in time
Hi Adam,
h
On Sat, 2017-11-11 at 13:03 +, Mark Morgan Lloyd wrote:
> Apologies for something which is distro related, but I was bitten by
> a
> "silly mistake"- one of my own, I hasten to say- earlier.
>
> Several legacy programs written in Delphi ground to a halt this
> morning,
> which turned out t
On Sat, Nov 11, 2017 at 2:03 PM, Mark Morgan Lloyd <
markmll.pgsql-gene...@telemetry.co.uk> wrote:
> Apologies for something which is distro related, but I was bitten by a
> "silly mistake"- one of my own, I hasten to say- earlier.
>
> Several legacy programs written in Delphi ground to a halt thi
Apologies for something which is distro related, but I was bitten by a
"silly mistake"- one of my own, I hasten to say- earlier.
Several legacy programs written in Delphi ground to a halt this morning,
which turned out to be because a Debian system had updated its copy of
PostgreSQL and restar
Hi all,
while writing test cases for my SQL pretty printer tool[1], I found what seems
a discrepancy in the "Type Casts" documentation[2]: it states that the two
syntaxes are equivalent, but while
CREATE TABLE contracts (
...
company_id uuid NOT NULL,
validity daterange NOT NULL,
15 matches
Mail list logo
