be reported on
the pgAdmin mailing lists --- I'm not sure that any of the pgAdmin
hackers read this list.
I do read the list, though I missed it initially.
I doubt it's a pgadmin bug, but let's see the query first.
Regards,
Andreas
---(end of broadcast)-
mined
from the first SELECT. Changing the order to have SELECT 1 does the job too.
Regards,
Andreas
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
> [Überflieger]). so is this a libc bug?
The sort order is correct, so libc did succeed in its part. Maybe your
terminal is having issues with utf-8? If you're using xterm: Did you
run it with -u8 or some utf-8-enabling X-resource? To verify that the
terminal is working properly, typing
Sorry, I just reread your mail: Your MUA is declaring it with
> Content-Type: text/plain; charset=unknown-8bit
This makes it even harder to discuss problems with Umlauts :-).
Andreas Seltenreich schrob:
> Klaus Ita schrob:
>
>> another "funny" thing is:
>>
>&
Details:
I was able to crash pgAdmin III when I attempted to add a Login Role.
Which pgAdmin version is that?
I can't reproduce this with pgAdmin 1.4Beta1.
Please post reply and further pgAdmin related stuff to pgadmin-support.
Regards,
Andreas
---(end of broa
ow
This is a known problem, not easily solved (not in 1.4.0).
When refreshing, you're destroying program structures used by the open
dialog. Advice: don't do this.
Regards,
Andreas
---(end of broadcast)---
TIP 4: Have
The following bug has been logged online:
Bug reference: 2090
Logged by: Andreas Schmidt
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Linux
Description:error in man-page of postmaster
Details:
'man postmaster' describes the
Is COPY foo TO STDOUT BINARY supposed to work? The query will run some
time, but won't give a result.
I couldn't see any mentioning in the COPY command docs that would
prohibit use of this combination.
Tested with psql on 8.0.5 and 8.1.1.
Regards,
Andreas
Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> writes:
Is COPY foo TO STDOUT BINARY supposed to work?
I don't think psql will do anything particularly sane with binary copy
data, if that's what you meant.
echo "COPY foo TO STDOUT BINARY;" | psql >ba
Jon Keating wrote:
I have a database with the default encoding set to EUC_JP and the client
(using pgAdmin III) is set to EUC_JP as well.
pgAdmin uses Unicode (unless the DB is SQL_ASCII or MULE_INTERNAL), you
won't get happy if you change it using a SET command.
Regards,
An
The following bug has been logged online:
Bug reference: 2152
Logged by: Andreas Kretschmer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Debian/Linux
Description:psql crash reproducible
Details:
i wrote a wrong query, and psql crash
The following bug has been logged online:
Bug reference: 2240
Logged by: Andreas Erber
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.2
Operating system: Windows XP
Description:length() with geometric types
Details:
Hi,
I discovered some strange
more useful.
Thx
CU
ae
James William Pye schrieb:
> On Mon, Feb 06, 2006 at 02:41:39PM +, Andreas Erber wrote:
>> Hi,
>>
>> I discovered some strange behaviour:
>> The length() function returns different results depending on the geometric
>> data type used as arg
The following bug has been logged online:
Bug reference: 2306
Logged by: Andreas Jung
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.9
Operating system: Linux
Description:Duplicate primary key
Details:
Ihave the following table (with 'id' as p
type
export LANG=C pgadmin &
This is a wrong advice.
Mete, use the option dialog to select your favourite language. Don't
touch the environment.
Regards,
Andreas
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
The following bug has been logged online:
Bug reference: 2390
Logged by: Andreas Kretschmer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Debian Linux
Description:check constraint
Details:
i want to add a check constraint like
e restored.
This is the original output from pg_restore. pgAdmin will also log the
precise parameters used to restore in the first log line, it might help
to see those.
Regards,
Andreas
---(end of broadcast)---
TIP 9: In versions below 8.0, the pl
The following bug has been logged online:
Bug reference: 5675
Logged by: Andreas Pflug
Email address: pgad...@pse-consulting.de
PostgreSQL version: 8.4.4
Operating system: Linux 2.6.26 i686
Description:out of memory at request size 32Mb
Details:
A slony 2.0 cluster
Am 24.09.10 14:54, schrieb Robert Haas:
On Fri, Sep 24, 2010 at 8:42 AM, Andreas Pflug
wrote:
The following bug has been logged online:
Bug reference: 5675
Logged by: Andreas Pflug
Email address: pgad...@pse-consulting.de
PostgreSQL version: 8.4.4
Operating system
The following bug has been logged online:
Bug reference: 5695
Logged by: Andreas Barth
Email address: aba+postgre...@not.so.argh.org
PostgreSQL version: 8.3.11
Operating system: Debian Linux (amd64)
Description:select into duplicates oid when using order by int
The following bug has been logged online:
Bug reference: 5705
Logged by: Andreas Karlsson
Email address: andr...@proxel.se
PostgreSQL version: 9.1
Operating system: Linux
Description:btree_gist: Index on inet changes query result
Details:
Hi,
I was looking at the
The following bug has been logged online:
Bug reference: 5843
Logged by: Andreas Kretschmer
Email address: akretsch...@spamfence.net
PostgreSQL version: 9.1
Operating system: all
Description:documentation error
Details:
the doku contains a bug:
http
ration and use a
> "boolean not null"?
Sounds much too straight forward, not mysql-ish artistic enough...
Regards,
Andreas
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
/interactive/sql-keywords-appendix.html)
You can have a 8.4 DB with a 'new' column and dump it with 8.4 tools.
You can have a 9.x DB with a 'new' column and dump it with 9.x tools.
However, it fails when you use 9.x pg_dump against 8.4 with a 'new' column
n 8.3.
http://www.postgresql.org/docs/9.1/static/release-8-3.html
--
Andreas Karlsson
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged on the website:
Bug reference: 7652
Logged by: Andreas H.
Email address: andreas.hei...@web.de
PostgreSQL version: 9.2.1
Operating system: any
Description:
It seems, that none of the functions in the section "Additional Sup
libpq++ is not compilable on Digital Unix since the line
using namespace std;
has been included into interfaces/libpq++/pgconnection.h probably because of
Irix.
Andreas Kardos
I have tested the pg_dumpall (with PATHNAME stuff) which Peter E. has mailed
to this list.
It works fine on QNX4 but definitly not on Digital Unix.
The version in CVS works in general, but not on QNX4. On QNX4 I have to
remove the escape backslashes.
Andreas Kardos
-Ursprüngliche
Of course, Digital Unix is more important than QNX. For now I can live with
the solution to remove the escape backslashes from pg_dumpall.
But we should keep this problem in mind. Unix portable shell programming is
not a nice matter...
Andreas Kardos
-Ursprüngliche Nachricht-
Von: Peter
.usesuper to true only, but not pg_user.usecatupd. The only
way
> to set pg_user.usecatupd to true is on creation.
>
> Is this a bug?
>
> Andreas Kardos
>
>
This seems to be a Sun Sparc (-fPIC).
On mine (SunOS 5.4/ Solaris 2.4) isn't any . Therefore libpq++ is
not compilable on this machine (native compilers).
configure sets HAVE_CXX_STRING_HEADER correctly (no).
Andreas Kardos
-Ursprüngliche Nachricht-
Von: Tom Lane <[EMAIL P
the GROUP BY list.
select tabname from systables group by 1 having 2 > 1;
all rows returned
select tabname from systables group by 1 having 1 > 2;
no rows found
Andreas
---(end of broadcast)---
TIP 2: you can get off all lists at
101 - 132 of 132 matches
Mail list logo
