Am 18.05.2017 um 22:43 schrieb Dave Page:
> Not to me, because the number of people I've had complimenting pgAdmin 4
> is probably 20x the number who have said they don't like it. Which is a
> good sign - normally people who don't like something are far more likely
> to say something.
People who
Hello,
on the 'Definition' tab in role properties 'valid until' is named 'Account
expires'. This is not correct. It's the password and not the account that
expires and therefore affects roles for which password authentication methods
(password or md5) are being used only.
Best regards,
Peter
Am 07.03.2015 um 13:32 schrieb Raymond O'Donnell:
It works fine for me - Windows 7 Home on my laptop, 64-bit, with pgAdmin
III 1.20.0. The interface flashes as described in the message linked
above - presumably as pgAdmin spawns and interacts with a new process
for pg_dump - but the entire opera
Am 06.03.2015 um 19:33 schrieb Raymond O'Donnell:
pgAdmin just uses pg_dump [1] to do the actual backup, so it would be
interesting to run pg_dump directly at the command line to see if the
same behaviour manifests itself.
There's nothing interesting about that, because this behaviour is reall
Hello,
tested it with 1.18.0 - looks fine.
( Comments on databases are visible again. )
( Default backup format is custom. )
Thank you very much!
Best regards,
Peter
P.S. guru hints are still blank?
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make cha
Hello,
Gesendet: Freitag, 02. August 2013 um 19:45 Uhr
Von: "Dave Page"
Betreff: Re: [pgadmin-support] PgAdmin V 1.16.1 Error - Comment on database
On Thu, Aug 1, 2013 at 12:13 PM, Jan-Peter Seifert
> > backups:
> > -you don't see which database/schema is being dumpe
Hello,
Gesendet: Dienstag, 20. August 2013 um 09:32 Uhr
Von: "Dave Page"
An: "Dinesh Kumar"
Cc: "pgadmin-support@postgresql.org" , "John Foelster" , "Dhiraj Chawla"
Betreff: Re: [pgadmin-support] Password setting having somewhat bizarre results.
Thanks Dinesh - patch applied.
I noticed o
Am 01.08.2013 08:40, schrieb Oli Noname:
> PgAdmin V 1.16.1 (on Win7) with Postgres 9.1 Server doesn´t show the
> Comments on a Database. Neither in SQL Field then in Preferences.
>
> I can overwrite the comments but i still doesn´t show any comment on
> database but the new set comment can be see
Hello Andi,
> Gesendet: Freitag, 15. März 2013 um 15:57 Uhr
> Von: "Andreas Laggner"
> "Failed to write to history file!" if the script ended successfully
you should check the path to the history file under:
Datei(File) -> Optionen (Options) -> Abfragewerkzeug (SQL Query Tool) ->
History file
Hello,
Original-Nachricht
> Datum: Sat, 23 Feb 2013 15:56:50 +0100
> Von: Guillaume Lelarge
> An: "Manuel Fdez (JVR)"
> CC: pgadmin-support@postgresql.org
> Betreff: Re: [pgadmin-support] Problem with pgAdmin and Server Status encode
> Well, I don't know spanish but I can gues
Hello,
Am 23.08.2012 12:33, schrieb Roland Kaschek:
> I try to get an instance of Postgres 9.1.5 ready for some SQL
> programming. I have installed the software along with Drupal 7 and
> mediaWiki. After starting the pgAdmin III it tells me the server is
> running. So I try to connect to it using
Hello,
another thing came to my mind.
pgAdmin III 1.14 does seem to commit the changes as soon as the new
value has been entered.
Wouldn't it be nice to display a warning or do a rollback if more than
one row had been updated instead of one or none then?
Thank you very much,
Peter
--
Sent via
Hello,
thank you very much for your feedback everyone!
Am 14.07.2012 15:06, schrieb Dave Page:
> > it would be nice to have additional/other fallback options ( via
> check box in pgAdmin's general options? ) to identify rows for
> editing in tables without primary keys.
> > > I'
Hello,
I have a feature request for the 'Edit data' window that is available for each
table in pgAdmin.
As the OID column is not guaranteed to contain unique OIDs it would be nice to
have additional/other fallback options ( via check box in pgAdmin's general
options? ) to identify rows for edi
Hello,
I often work with different major versions of PostgreSQL and prefer to use the
pg_dump version of the server.
However, you can only set 'PG bin path' once for all versions of pgAdmin III.
So sometimes I forget to change the versions and the dump can't be restored
without problems.
So i
t;>
> >>> ---- Original-Nachricht
> >>>> Datum: Tue, 11 Jan 2011 23:52:11 +0100
> >>>> Von: Guillaume Lelarge
> >>>> An: Jan-Peter Seifert
> >>>> CC: pgadmin-support@postgresql.org
> >>>> Betreff:
ersions
> Le 16/02/2011 19:41, rleonanaya a écrit :
> >
> >
> > Guillaume Lelarge-3 wrote:
> >>
> >> Le 12/01/2011 18:23, jan-peter.seif...@gmx.de a écrit :
> >>> Hello,
> >>>
> >>> Original-Nachricht ----
> >&g
Hello,
Am 05.03.2011 15:51, schrieb Maximilian Tyrtania:
> For some reason PGAdmin 1.12.2 would show "Logs are not available for this
> server" (well, actually "Logs sind für diesen Server nicht verfügbar", the
> translation is mine) in the logs pane when i want to view the log file via
> the
Hello,
text autocompletion prevents creating a database with LATIN1 as encoding as
long as there's no other LATIN1 database on a server that has been initialized
with locale de_DE.UTF-8 and UTF-8 as encoding (on Ubuntu).
As soon as you type in 'de_DE' in the fields for LC_COLLATE and LC_CTYPE
Hello,
Original-Nachricht
> Datum: Tue, 11 Jan 2011 23:52:11 +0100
> Von: Guillaume Lelarge
> An: Jan-Peter Seifert
> CC: pgadmin-support@postgresql.org
> Betreff: Re: [pgadmin-support] 1.12.1 - cannot dump from older server versions
I've compared th
Hello,
Am 06.01.2011 12:11, schrieb Guillaume Lelarge:
I have problems dumping databases on older server versions (e.g. 8.4)
>>> with pgAdmin 1.12.1. It seems to enter an endless loop after clicking 'OK'.
>>> It doesn't matter whether the binaries path points to v8.4 or v9.0. Dumping
>>> fro
Hello,
sorry for barging in.
In German you can both - software and hardware - call a server indeed:
http://de.wikipedia.org/wiki/Server
As PostgreSQL servers don't have a name by themselves people familiar
with PostgreSQL know that they have to enter the host's address.
Both server and host are
Hello,
> somehow this seems to be connected to PostgreSQL schemata. The dump of
> another database with only the public schema completes fast and without
> problems.
> The database that causes problems has four additional schemata - each
> owned by a different user and more privileges are given on
and Happy New Year!
>
> Original-Nachricht
> > Datum: Wed, 08 Dec 2010 15:39:59 +0100
> > Von: Guillaume Lelarge
> > An: Jan-Peter Seifert
> > CC: pgadmin-support@postgresql.org
> > Betreff: Re: [pgadmin-support] 1.12.1 - cannot dump from older s
Hello and Happy New Year!
Original-Nachricht
> Datum: Wed, 08 Dec 2010 15:39:59 +0100
> Von: Guillaume Lelarge
> An: Jan-Peter Seifert
> CC: pgadmin-support@postgresql.org
> Betreff: Re: [pgadmin-support] 1.12.1 - cannot dump from older server versions
> L
Hello,
I have problems dumping databases on older server versions (e.g. 8.4) with
pgAdmin 1.12.1. It seems to enter an endless loop after clicking 'OK'. It
doesn't matter whether the binaries path points to v8.4 or v9.0. Dumping from
9.0 works fine.
I have 8.3 (pg_installer, two instances/servi
Hello,
sorry if this is already known.
In order to test a script I gave privileges on a schema different from
public and a function and a table therein to a 'normal' login role:
CREATE ROLE rolle LOGIN
ENCRYPTED PASSWORD ''
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
When I choose the
Hello,
there are two dialogues in pgAdmin III where buttons get deactivated for
no obvious reasons.
Backup:
If a schema is chosen for backup the BLOB option is greyed out. However,
according to the docs (
http://www.postgresql.org/docs/8.4/static/app-pgdump.html ) BLOBs are
only being dumped if u
Hello,
there seems to be a problem with evaluating the ACL for a procedural language:
SQL windows says:
-- Language: plpgsql
-- DROP LANGUAGE plpgsql;
CREATE TRUSTED PROCEDURAL LANGUAGE 'plpgsql'
HANDLER plpgsql_call_handler
VALIDATOR plpgsql_validator;
ALTER LANGUAGE plpgsql OWNER TO user
Hello,
Guillaume Lelarge wrote:
> > However, when I view the properties of the new template1 in pgAdmin III
> it
> > isn't stated that it's a system database anymore. Is it because that the
> > OID is different from 1 or is there a hidden flag? In pg_database I
> don't
> > see any significant di
Hello,
in order to get a clean template1 I dropped and recreated it:
UPDATE pg_database SET datistemplate = false WHERE datname = 'template1';
DROPDB -U postgres template1
CREATEDB -U postgres -T template0 template1
UPDATE pg_database SET datistemplate = true WHERE datname = 'template1';
GRANT
Hello,
when you create a new database with pgAdmin III 1.10 beta 2 specifying a locale
different from the server pgAdmin sends a wrong CREATE DATABASE syntax to the
server - COLLATE instead of LC_COLLATE and CYTPE instead of LC_CTYPE.
http://www.postgresql.org/docs/8.4/static/sql-createdatabase
32 matches
Mail list logo
