On Thu, Aug 25, 2011 at 10:50:55PM +0200, Guillaume Lelarge wrote:
> On Thu, 2011-08-25 at 20:21 +, Cuddihy, Joe wrote:
> > Hello
> > We are trying to recover our postgres data base for the Avocent data center
> > planner tool. We are in need of the admin password for the database. The
> > or
On Thu, 2011-08-25 at 20:21 +, Cuddihy, Joe wrote:
> Hello
> We are trying to recover our postgres data base for the Avocent data center
> planner tool. We are in need of the admin password for the database. The
> original installer is no longer working here. Any way to find the admin
> pass
Hello
We are trying to recover our postgres data base for the Avocent data center
planner tool. We are in need of the admin password for the database. The
original installer is no longer working here. Any way to find the admin
password and or be able to change it.
Any help will be greatly apprec
Willy-Bas Loos wrote:
> I've encountered this before, psql gives me a syntax error for no
> clear reason. It's allways on the first character of a sql file.
> The file is in the attachment
hexdump says the first three bytes of that file are:
ef bb bf
http://en.wikipedia.org/wiki/Byte_ord
Le 04/12/2010 02:45, Josh Berkus a écrit :
>
>> I've encountered this before, psql gives me a syntax error for no clear
>> reason. It's allways on the first character of a sql file.
>> I think that there must be some strange character code at the first
>> position, maybe it is because i share a nt
> I've encountered this before, psql gives me a syntax error for no clear
> reason. It's allways on the first character of a sql file.
> I think that there must be some strange character code at the first
> position, maybe it is because i share a ntfs partition with the windows
> installation on m
Hi,
I've encountered this before, psql gives me a syntax error for no clear
reason. It's allways on the first character of a sql file.
I think that there must be some strange character code at the first
position, maybe it is because i share a ntfs partition with the windows
installation on my lapt
Lukasz Brodziak writes:
> I have a problem with viewing tables from my DB. The interesting thing
> is that the physical files exist in the data folder but only some of
> them are visible both in pgAdmin and the application that uses the DB.
> What's more there's no trace of those tables in pg_clas
Le 19/12/2009 16:16, Guillaume Lelarge a écrit :
> Hi,
>
> Le 01/09/2009 09:15, PESTY Benoit a écrit :
>> [...]
>> It was my first idea to have the background color of the tool completely
>> changed. But it is probably too "invasive" and will completely kill the
>> readability.
>>
>> Maybe just
noit Pesty
-Message d'origine-
De : Guillaume Lelarge [mailto:guilla...@lelarge.info]
Envoyé : mardi 1 septembre 2009 08:27
À : pgadmin-support@postgresql.org
Cc : PESTY Benoit
Objet : Re: [pgadmin-support] [ADMIN] Background color in query tool
Hi,
Le lundi 24 août 2009 à 09:23:34,
Hi,
Le lundi 24 août 2009 à 09:23:34, PESTY Benoit a écrit :
> [...]
> The new option to define a background color for each server in PgAdmin
> 1.10 is very cool (to distinguish test servers from production servers).
>
> It would be very nice to have a reminder of this background color in the
> qu
Hi,
Le lundi 24 août 2009 à 09:23:34, PESTY Benoit a écrit :
> [...]
> The new option to define a background color for each server in PgAdmin
> 1.10 is very cool (to distinguish test servers from production servers).
>
> It would be very nice to have a reminder of this background color in the
> qu
Hello,
The new option to define a background color for each server in PgAdmin
1.10 is very cool (to distinguish test servers from production servers).
It would be very nice to have a reminder of this background color in the
query module.
Best Regards,
Benoit Pesty
--
Sent via pgadmin-support
We are running postgresql server and phppgadmin on a Centos server with
cpanel. Both show up in within the cpanel. We can create databases and
users. But when we log into phppgadmin the postgresql server is listed with
a RED x and when we try to log in to the postgresql server we can't. Any
idea wh
Firstly, I think this is a little in-depth for a mailing list, and
reading the manual will certainly help you out :)
Secondly, what exactly are you trying to do? As all I can see your
script doing is reading the amount of disk space used on each device,
and if it's greater than 90% used, e-ma
To all who want unsubscribing, it is best to fill out this form:
http://www.postgresql.org/community/lists/subscribe
Regards,
Andy.
On 2/22/07, jose carlos de la toba duarte <[EMAIL PROTECTED]> wrote:
Hi..
Please unsubscribe me.
Thanks
Jose Carlos
_
Hi..
Please unsubscribe me.
Thanks
Jose Carlos
_
Live Search en Prodigy/MSN. Todo lo que buscas ahora más rapido
http://live.com
---(end of broadcast)---
TIP 5: don't forge
maybe you should read on how to unsubscribe ;)
On 2/22/07, VivekanandaSwamy R. <[EMAIL PROTECTED]> wrote:
Hi..
Please unsubscribe me.
Thanks
Vivek.R
Information transmitted by this e-mail is proprietary to Infinite
Computer Solutions and / or its Customers and is intended for use only
Andy Shellam (Mailing Lists) wrote:
> Hi,
>
> I have PgAdmin 1.6.2 talking to a PostgreSQL 8.2.3 server with the
> distributed admin pack installed (from source's contrib/adminpack), and
> have ran the adminpack.sql script against the postgres database. If, in
> PgAdmin, I click Tools > Server St
Hi,
I have PgAdmin 1.6.2 talking to a PostgreSQL 8.2.3 server with the
distributed admin pack installed (from source's contrib/adminpack), and
have ran the adminpack.sql script against the postgres database. If, in
PgAdmin, I click Tools > Server Status and select the "logfile" tab, I
get th
Vinayak,
Please don't post twice to two different lists (four of the same posts
to both pgsql-admin and pgadmin-support.)
This clearly isn't a problem with PG Admin - so don't clutter that list
up, and don't multiple-post - it won't change anything posting twice,
and if anything you'll only en
Jeanna Geier Wrote:
- In the docs, it says that when using SSL in Postgres "This requires that
OpenSSL is installed on both client and server systems and that support in
PostgreSQL is enabled at build time" - is this correct? Or can we use the
certificates and keystore file we generated using
Yes!
I followed exactly that page to do.
Thanks
Scott Marlowe escreveu:
On Wed, 2006-07-12 at 15:04, Alexander Burbello wrote:
Ok! Its a good tool, but for Production Database I think it is not
recommended.
Only using pg_dump for the second backup plain.
Suppose that you backed up at 6:
On Wed, 2006-07-12 at 15:04, Alexander Burbello wrote:
> Ok! Its a good tool, but for Production Database I think it is not
> recommended.
> Only using pg_dump for the second backup plain.
> Suppose that you backed up at 6:00am and at 9am happened a crash on the
> server.
> In this case, I would
Ok! Its a good tool, but for Production Database I think it is not
recommended.
Only using pg_dump for the second backup plain.
Suppose that you backed up at 6:00am and at 9am happened a crash on the
server.
In this case, I would lost data between that time, 3 hours of information.
For product
On 7/11/06, Burbello <[EMAIL PROTECTED]> wrote:
I need to test and create a procedure to restoredatabases.Why not just use pg_dump?See http://manual.intl.indoglobal.com/ch06s07.html
- it's really easy. This is how we copy from production to testing and development and how we do nightly backups. =
You should try it as follows:
create or replace function subfun1(int8) returns record
as'declare rec record;begin
select ename as ename,mgr as mgr into rec from emp where empno=$1
; return
rec;end;'language'plpgsql';
-
selec
Daniel Struck wrote:
If you decrypt the data on the database, the sysadmin can see it.
Hm, you are right. If one does decrypt the data on the database you have to sent
the password to postgresql and so a administrator of the database could easily grasb
the password.
So the only way to go, wo
On Sat, Oct 05, 2002 at 08:17:38PM -0700, Nikolaus Dilger wrote:
> Raymond,
>
> Partitioned tables would solve your issue since you
> could just truncate a partiotion in order to delete the
> unneeded data. Unfortunately they are not available in
> PostgreSQL. But maybe in a future release.
>
Raymond,
Partitioned tables would solve your issue since you
could just truncate a partiotion in order to delete the
unneeded data. Unfortunately they are not available in
PostgreSQL. But maybe in a future release.
Unfortunately you also cannot use a UNION ALL in a view
to fake partitions.
So
On Wed, 2 Oct 2002, Raymond Chui wrote:
> I have some tables with huge data.
> The tables have column timestamp and float.
> I am try to keep up to 6 day of data values.
> What I do is execute SQL below from crontab (UNIX to
> schedule commands).
>
> BEGIN;
> DELETE FROM table_1 WHERE column_time
On Wed, 2002-08-14 at 13:09, Raymond Chui wrote:
> Let say I have a table has column1 and column2 and I made a trigger for
> after INSERT OR UPDATE for each row to execute procedure my_function.
>
> What I want is the trigger execute my_function only when column1 is
> insert or
> update, but not
32 matches
Mail list logo
