Hello,
The Types list in the pgAdmin treeview doesn't seem to include user
types whose names begin with underscores. Eg. if I run
CREATE TYPE my_type1 AS (val integer);
CREATE TYPE _my_type2 AS (val integer);
my_type1 is shown, but _my_type2 is not. (I even tried enabling "Show
Syste
enabled and selecting
that causes a segfault.
On 28/12/2012 3:04 AM, Guillaume Lelarge wrote:
On Thu, 2012-12-27 at 16:58 +0100, Guillaume Lelarge wrote:
On Tue, 2012-12-25 at 18:38 +1100, Evan Martin wrote:
Thanks, Guillaume. It's ticket 386, right?
Yes.
Could you also add shortcut
/2012 12:48 AM, Guillaume Lelarge wrote:
On Wed, 2012-12-05 at 20:12 +1100, Evan Martin wrote:
You mean pressing the shorcut key right after the server status has
refreshed, so the selection is on a different row? Couldn't the same
thing happen with the toolbar button? Anyway, I have a suggest
xists simply select no row (ie. clear the selection). The button
or shorcut key would then be disabled.
On 5/12/2012 8:01 PM, Guillaume Lelarge wrote:
On Wed, 2012-12-05 at 19:28 +1100, Evan Martin wrote:
You're right, the third button does exactly what I want, I just didn't
know about
o seem to be in this category. Are
there shortcut keys for them? If not, that would be very useful.
Regards,
Evan
On 4/12/2012 11:25 PM, Guillaume Lelarge wrote:
On Mon, 2012-12-03 at 21:53 +1100, Evan Martin wrote:
Is there any way to get the full query text for a given process in the
Serve
Thanks, confirmed fixed on trunk.
On 4/12/2012 12:24 AM, Dave Page wrote:
On Mon, Nov 26, 2012 at 8:08 AM, Guillaume Lelarge
wrote:
On Sun, 2012-11-25 at 14:47 +, Dave Page wrote:
On Sunday, November 25, 2012, Guillaume Lelarge wrote:
On Fri, 2012-11-23 at 00:22 +1100, Evan Martin
Is there any way to get the full query text for a given process in the
Server Status window? The Query column shows the start of it, so I
presume pgAdmin has the whole thing, but is not showing it. If it's not
currently possible please add it! Something like a "copy query to
clipboard" context
t new, it happened before the fix as
well, I just forgot to mention it.
On 27/11/2012 5:21 PM, Akshay Joshi wrote:
On Tue, Nov 27, 2012 at 12:11 AM, Dave Page <mailto:dp...@pgadmin.org>> wrote:
Hi
On Fri, Nov 23, 2012 at 2:26 AM, Evan Martin
mailto:postgre...@rea
Running latest trunk build on 32-bit Linux, pgAdmin crashes whenever I
click on a schema that contains one or more domains.
GDB backtrace: http://pastebin.com/mSGd978J
To reproduce:
1. Create a new database
2. Create a new schema in the database
3. Create a new domain in the schema.
pgAdmin c
r the behaviour is correct for some
functions but incorrect for other. However it should be quite clear
which condition makes the button active at begining.
On 22.11.2012 13:55, Evan Martin wrote:
This crash happens to me every time both on 1.16.0 running on Windows
7 x64 and on latest trunk v
This crash happens to me every time both on 1.16.0 running on Windows 7
x64 and on latest trunk version running on 32-bit Linux.
To reproduce:
1) Open the properties dialog for a function.
2) On the options tab check "Security of definer".
3) Click Apply.
4) Uncheck "Security of definer again".
I've had this happen regularly as well (on Windows 7 x64), though I
cannot reproduce it reliably. Also fully agree on auto-recovering the
users work, I'd love to see that implemented.
On 19/08/2012 8:02 AM, Thangalin wrote:
Hi,
* Platform - Windows XP Professional (32-bit)
* Language - Englis
Running the latest trunk build (g7ac0c60)
When pgAdmin displays the query output in a grid each column seems to be
sized based on the header size and the value is truncated as needed.
There is no indication that it's been truncated. This sometimes makes
the result highly misleading and I've ju
07-14 at 01:26 +1000, Evan Martin wrote:
No comments at all? Can anyone else at least repro this?
Don't know for others, but I was overloaded translating in french the
PostgreSQL 9.2 manual. Now that's it's done, I can get back on hacking
pgAdmin.
On 6/07/2012 10:33 PM, Evan
No comments at all? Can anyone else at least repro this?
On 6/07/2012 10:33 PM, Evan Martin wrote:
I've reliably reproduced the freezing bug I mentioned before (in the
suggestion to save query text). pgAdmin freezes when I try to run a
backup file created by pg_dump from an SQL query w
I've reliably reproduced the freezing bug I mentioned before (in the
suggestion to save query text). pgAdmin freezes when I try to run a
backup file created by pg_dump from an SQL query window. The file
contents look like this:
COPY much_data (some_data) FROM stdin;
BLAH/BLAH/BLAH/BLAH/BLAH/BL
Fixing the bug and implementing this are not mutually exclusive. Of
course, it should be fixed, but that's just one bug. I've experienced at
least 3 different kinds of crashes. This is about mitigating the impact
of all crashing bugs, which is important, because they will never be
eliminated co
I often have multiple SQL query windows open in pgAdmin (v1.14.3 on
Windows 7 x64). From time to time pgAdmin will crash or freeze (become
unresponsive) and would have to be killed. When this happens all unsaved
query text is lost, which is extremely frustrating. It's by far the
biggest problem
I'm running pgAdmin 1.14.0 on Windows 7 x64. I created a database named
"%" on my PostgreSQL 9.1.1 server. Clicking on this database in the
treeview immediately crashes pgAdmin every time. Some details from the
event log:
Faulting application name: pgAdmin3.exe, version: 1.14.0.5, time stamp:
g an object that no longer exists (eg. the columns
for a table that has been dropped) should detect this and refresh (at
the appropriate level). At minimum, it should give some indication that
the object doesn't exist, rather than the misleading impression that it
has no children.
Than
20 matches
Mail list logo
