> --- Original Message ---
> From: Guillaume Lelarge <[EMAIL PROTECTED]>
> To: Laurent ROCHE <[EMAIL PROTECTED]>
> Sent: 19/06/07, 17:33:02
> Subject: Re: Using many pg_dump in pgAdmin (aka Re : Re :
> [pgadmin-support]pg_dump: ALTER SEQUENCE ... OWNED in 8.1)
>
> Laurent ROCHE a écrit
Laurent ROCHE a écrit :
> Just to clarify what I mean.
> I am quite happy (or should I say: not too unhappy) to juggle with different
> version of pg_dump in my scripts.
> If that's the way it has to be, that's the way it has to be.
> See point A, below.
>
> But to me pgAdmin is a tool that must
Hi,
Just to clarify what I mean.
I am quite happy (or should I say: not too unhappy) to juggle with different
version of pg_dump in my scripts.
If that's the way it has to be, that's the way it has to be.
See point A, below.
But to me pgAdmin is a tool that must be easy to use.
Hence, as it seem
On 2007-06-19 10:29, Dave Page wrote:
(...)
cp -f ./pgadmin/include/images/elephant48.xpm
%{buildroot}/%{_datadir}/%{name}/%{name}.xpm
And that should fix it. I've made the change in SVN already.
And it did it. In fact firstly I thought it was problem with your
makefile not with spec.
I al
>I knw that I have to use include instead of excluding the tables.Do I
have to include each and
>>every tables manually or is there way to do that?
There's no guarantee. but the following query might be a
good starting point to build your include list.
It selects only tables with less than 3000
On 19/06/2007 14:36, Dave Page wrote:
Raymond O'Donnell wrote:
Agreed - an option in the preferences to specify the path to the desired
pg_dump would certainly be useful.
Already in the next release.
Great!
another one with all compatible tools versions to be able to work
correctly on d
Raymond O'Donnell wrote:
> On 19/06/2007 13:54, Laurent ROCHE wrote:
>
>> May be that's a pg_dump issue: it should be compatible with the
>> server it connects to, and not to its own version ?
>
> What do you mean?
Shipping every version of pg_dump, libpq & supporting DLL's back to v7.3
by the s
On 19/06/2007 13:54, Laurent ROCHE wrote:
May be that's a pg_dump issue: it should be compatible with the
server it connects to, and not to its own version ?
What do you mean?
Still meanwhile I would think pgAdmin should allow installing other
pg_dump executable.
I'm fairly sure that pgAdm
OK, I understand that.
May be that's a pg_dump issue: it should be compatible with the server it
connects to, and not to its own version ?
Still meanwhile I would think pgAdmin should allow installing other pg_dump
executable. And it should switch from one to another to be able to generate a
c
I'm getting errors upgrading from 1.6.2-1~pgaoetch1 to 1.6.3-1~pgaoetch1
via the UK mirror ftp2.uk.postgresql.org
Get: 1 ftp://ftp2.uk.postgresql.org etch/pgadmin pgadmin3
1.6.3-1~pgaoetch1 [4330kB]
Get: 2 ftp://ftp2.uk.postgresql.org etch/pgadmin pgadmin3-data
1.6.3-1~pgaoetch1 [2722kB]
Fetc
Regarding pgadmin3-data
File on mirror(s) = 2722978 bytes
Size in "Packages"/apt-cache show = 2722412
Obviously this causes an error:
Failed to fetch
ftp://ftp2.uk.postgresql.org/sites/ftp.postgresql.org/pgadmin3/release/debian/dists/etch/pgadmin/binary-all/misc/pgadmin3-data_1.6.3-1~pgaoetch1_a
Marcin Zajączkowski wrote:
cp: cannot stat `./src/include/images/elephant48.xpm': No such file or
directory
Were there some changes with graphic files?
Yeah, in fact the entire src/ tree moved to pgadmin/.
In the spec file, change the line:
cp -f ./src/include/images/elephant48.xpm
%{build
On 2007-06-19 09:25, Dave Page wrote:
Marcin Zajączkowski wrote:
Sometimes (but rarer that 1.4) my pgadmin catches segmentation fault
when I want to close "edit grid" window. Last time I ran it from gdb
(stack trace below).
It's pgadmin 1.6.3 (rev. 6115) recompiled from SRPM for FC7 (with also
r
[please keep replies on list]
Eric Shuman wrote:
Hi Dave,
Thanks for the reply.
Typically I do run it from an init script. In this case the output just
goes to the login screen of the physical server, which is not too big of a
deal since I rarely use the system that way. (Though it would be n
Hi All,
I want to dump the database by using pg_dump command but the problem is the
version at the server is 7.4 which doesn't support the provision for
excluding tables as in version 8.2.
There are 500+ tables in the database,from which 15-20 are of huge sizes.I
want to exclude them.Is there a
Marcin Zajączkowski wrote:
Hi,
Sometimes (but rarer that 1.4) my pgadmin catches segmentation fault
when I want to close "edit grid" window. Last time I ran it from gdb
(stack trace below).
It's pgadmin 1.6.3 (rev. 6115) recompiled from SRPM for FC7 (with also
recompiled wxWidgets 2.8.3). I hav
16 matches
Mail list logo