On Sat, Aug 31, 2019 at 12:35 AM stan wrote:
> Got it working.
>
> Not 100% sure what I had wrong.
You can also do, in your session:
set client_min_messages to notice;
without having to change it in the configuration (for all sessions).
Luca
Hi,
I'm in the process of upgrading from 96 -> 11 (on RHEL 7.3) . Both the
versions have PostGIS 2.5.1 installed and working.
pg_upgrade fails with:
pg_restore: [archiver (db)] Error from TOC entry 440; 1259 537086 TABLE
tablename databasename
pg_restore: [archiver (db)] could not execute query:
Will Storey writes:
> On Sun 2019-09-01 19:46:19 -0400, Tom Lane wrote:
>> A separate question is how come the particular query you're complaining
>> about has (seemingly) a fairly wide window where it never does any
>> CHECK_FOR_INTERRUPTS call before terminating. Perhaps there's someplace
>> we
On Sun 2019-09-01 19:46:19 -0400, Tom Lane wrote:
> I poked at this for awhile and concluded that what you must be seeing is
> that the statement timeout interrupt triggers, but no CHECK_FOR_INTERRUPTS
> call happens thereafter, until we get to the disable_statement_timeout()
> call in finish_xact_
Will Storey writes:
> Thanks for the pointer!
> It looks like we'd have to be entering that section and finding the
> statement timeout not set, otherwise we'd not fall through to the "user
> request" case.
> But as far as I can tell, the only reason my query would be cancelled is
> because of t
Quoting Olivier Gautherot :
This is the specific error message:
Could not execute the SQL command.
Message returned: ERROR: column pr.proisagg does not exist
LINE 1: ...namespace AS ns ON pr.pronamespace = ns.oid WHERE pr.proisag...
^
HINT: Perhaps you meant to reference the column
--
"They
On Sun, Sep 1, 2019 at 6:35 AM stan wrote:
> On Sun, Sep 01, 2019 at 06:30:23AM -0400, stan wrote:
> > I apologize, as this is a bit off topic for this list.
> >
> > pgmodeler got mention in a thread that I started a day or two ago, and
> it looks
> > like it might be very useful
> >
> > I am ru
Hi
ne 1. 9. 2019 v 12:35 odesÃlatel stan napsal:
> On Sun, Sep 01, 2019 at 06:30:23AM -0400, stan wrote:
> > I apologize, as this is a bit off topic for this list.
> >
> > pgmodeler got mention in a thread that I started a day or two ago, and
> it looks
> > like it might be very useful
> >
> >
On Sun, Sep 01, 2019 at 06:30:23AM -0400, stan wrote:
> I apologize, as this is a bit off topic for this list.
>
> pgmodeler got mention in a thread that I started a day or two ago, and it
> looks
> like it might be very useful
>
> I am running on Ubuntu 18.04 (latest STABLE), and I found that
I apologize, as this is a bit off topic for this list.
pgmodeler got mention in a thread that I started a day or two ago, and it looks
like it might be very useful
I am running on Ubuntu 18.04 (latest STABLE), and I found that there is a
package,
which I downloaded. The idea is to import the pr
Tony:
On Sun, Sep 1, 2019 at 10:05 AM Tony Shelver wrote:
> I think you will find that most DBAs build their own scripts using tools like
> Perl or Python, or a commercial product.
Tools like Perl are great for building text output, it's got a lot of
shortcuts for a lot of things. Not that sure
Similar to what Francisco said. Not exactly sure what your use case is
though..
In the past I have usually used a DB modeling / design front end tool to
design my database, and then maintain and generate most of the build
scripts.
Datanamic Dezign used to be my go-to for SQL Server when i still p
12 matches
Mail list logo
