On Tue, Jan 30, 2018 at 06:31:32PM +, Raymond O'Donnell wrote:
>
> Thanks for your response, Johann.
>
> I'm probably being stupid, but I can't find those packages... I've
> been hunting in
> https://apt.postgresql.org/pub/repos/apt/dists/jessie-pgdg/ which
I have looked in the apt.postgresq
Chapman,
I am not PgAdmin support, but AFAIK, there never was, or are, any tables or
functions that PgAdmin is dependent on.
My guess is that the former dba or owner of the database in questionmade those
tables and functions as a shortcut or workaround to usingregular PostgreSQL
catalogs and fu
Hi,
In a database that has been around for a long, long time, there are
several pgAdmin-related relations and functions:
I assume these are things that were needed for some ancient version
of pgAdmin in some ancient version of PostgreSQL? I tried finding
something in current pgAdmin docs about th
On 29/01/18 08:12, Johann Spies wrote:
On Sun, Jan 28, 2018 at 04:17:17PM +, Raymond O'Donnell wrote:
However, I'm having problems installing it on my Debian Jessie laptop - I'm
probably doing something silly and would appreciate help:
I am running buster and had to temporarily change my s
On Tue, Jan 30, 2018 at 3:22 PM, Melvin Davidson
wrote:
> *>No - if you switch on "Show system objects", it will display system
> objects such as row *
> *>types. That's the whole point of the switch (which is off by default). *
>
> *Except that "system objects" are NOT USER tables, views, index
>No - if you switch on "Show system objects", it will display system objects
>such as row >types. That's the whole point of the switch (which is off by
>default).
Except that "system objects" are NOT USER tables, views, indexes, etc.
They are _system_ catalogs and views;
Your definition is a b
On Tue, Jan 30, 2018 at 2:57 PM, Melvin Davidson
wrote:
>
> *>Effectively, a composite type that can represent a row in a class*
>
> *That may be true, but users expect to see "user defined types", not
> tables and views. As such, the query driving the display should be
> something like:*
>
>
>
>
>Effectively, a composite type that can represent a row in a class
That may be true, but users expect to see "user defined types", not tables and
views. As such, the query driving the display should be something like:
WITH types AS
( SELECT reltype
FROM pg_class
WHERE relkind = 'c'
)
SELECT
I'm not sure on this but we have ported this behaviour from pgAdmin3.
May be someone else from the community can explain?
On Tue, Jan 30, 2018 at 4:16 PM, ldrlj1
wrote:
> Interesting... and thank you!
> While I did expect to see tableoid, cmax, xmax, cmin, xmin and ctid in my
> tables... I neve
On Tue, Jan 30, 2018 at 10:46 AM, ldrlj1
wrote:
> Interesting... and thank you!
> While I did expect to see tableoid, cmax, xmax, cmin, xmin and ctid in my
> tables... I never expected turning on "Show system objects" would show
> sequences and tables as Postgres Types.
>
> So I am knowledgeable,
Interesting... and thank you!
While I did expect to see tableoid, cmax, xmax, cmin, xmin and ctid in my
tables... I never expected turning on "Show system objects" would show
sequences and tables as Postgres Types.
So I am knowledgeable, can you explain why that happens?
--
Sent from:
http://w
I downloaded postgreSQL v. 9.6 and v. 10.0, and with both versions I keep
getting a message with the following: "Fatal Error. This application server
could not be contacted."
I tried uninstalling both versions of the software's and reinstalled as well as
rebooted my computer after installation.
12 matches
Mail list logo
