Woody and Albe-
I wasn't aware of pg_service -- that does solve my original problem.
Thanks for the replies.
-Reece
--
Reece Hart, http://harts.net/reece/, GPG:0x25EC91A0
On Mon, 2006-11-06 at 19:58 -0800, Reece Hart wrote:
> On Mon, 2006-11-06 at 16:43 -0800, Jeff Davis wrote:
> > You can use "ALTER DATABASE name RENAME TO newname;". Does that
> > help?
>
> This is what I do now to evolve from development to staging to
> production, as well as to deprecate version
Of Reece
HartSent: Monday, November 06, 2006 6:07 PMTo:
pgsql-generalSubject: [GENERAL] database name
aliases?
I'd like to be able to have several versions of a database available
concurrently and one database alias that refers to the most recent of
these. For
example:dbname_1-1dbn
Reece Hart wrote:
> I'd like to be able to have several versions of a database
> available concurrently and one database alias that refers to
> the most recent of these. For example:
>
> dbname_1-1
> dbname_1-2
> dbname_1-3
> dbname -> dbname_1-3
>
> and
> $ psql -d dbname
> would connect to d
On Mon, 2006-11-06 at 16:43 -0800, Jeff Davis wrote:
You can use "ALTER DATABASE name RENAME TO newname;". Does that help?
This is what I do now to evolve from development to staging to production, as well as to deprecate versions. That indeed solves most of the problem.
Aliases might s
On Mon, 2006-11-06 at 16:29 -0800, Reece Hart wrote:
> On Tue, 2006-11-07 at 04:54 +0500, Talha Khan wrote:
> > You can do this by using a script. I mean whenever you are creating
> > a new version of the database. you can do that by running a script
> > that creates a database and then stores the
On Nov 6, 2006, at 19:29 , Reece Hart wrote: On Tue, 2006-11-07 at 04:54 +0500, Talha Khan wrote: You can do this by using a script. I mean whenever you are creating a new version of the database. you can do that by running a script that creates a database and then stores the name of that dat
On Tue, 2006-11-07 at 04:54 +0500, Talha Khan wrote:
You can do this by using a script. I mean whenever you are creating a new version of the database. you can do that by running a script that creates a database and then stores the name of that database in an environmental variable . Now
Hi Reece,You can do this by using a script. I mean whenever you are creating a new version of the database. you can do that by running a script that creates a database and then stores the name of that database in an environmental variable . Now you can run psql by connecting to a database through
I'd like to be able to have several versions of a database available concurrently and one database alias that refers to the most recent of these. For example:
dbname_1-1
dbname_1-2
dbname_1-3
dbname -> dbname_1-3
and
$ psql -d dbname
would connect to dbname_1-3.
Any ideas?
Thanks,
Reece
"Envbop" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi
>
> I've just inherited a PostgreSQL database, for which I do not have any
> details of, like database name or the users.
> This used to be a library database which was managed via a web page
> written
> in php.
> Its runni
Hi
I've just inherited a PostgreSQL database, for which I do not have any
details of, like database name or the users.
This used to be a library database which was managed via a web page written
in php.
Its running on a Linux box.
The front end was also written in php. The original writers of this
Envbop wrote:
Can someone tell me where I can find the database names.
login using psql and type \l ;-)
chances are you have root access to the linux box, then you could modify
pg_hba.conf to gain some access
Do you have any account information at all?
---(end of broadcast
=?ISO-8859-1?Q?Michal_T=E1borsk=FD?= <[EMAIL PROTECTED]> writes:
> Is it possible to put a database name in slow query log?
7.5 will have a feature for this, but in existing releases you'd have to
hack up elog.c to do it.
regards, tom lane
---(end
Peter Eisentraut wrote:
> ADBAAMD writes:
>
>> Brian T. Allen wrote:
>>
>>> I just ran into that too, and find it most undesirable. I don't know
>>> whether that is part of the SQL spec or not, but it seems very odd. The
>>> queries seem to be converted to lowercase before they ever reach the
ADBAAMD writes:
> Brian T. Allen wrote:
>
> > I just ran into that too, and find it most undesirable. I don't know
> > whether that is part of the SQL spec or not, but it seems very odd. The
> > queries seem to be converted to lowercase before they ever reach the SQL
> > engine.
>
> Corre
Brian T. Allen wrote:
> I just ran into that too, and find it most undesirable. I don't know
> whether that is part of the SQL spec or not, but it seems very odd. The
> queries seem to be converted to lowercase before they ever reach the SQL
> engine.
Correct me if I'm wrong, but doesn
I just ran into that too, and find it most undesirable. I don't know
whether that is part of the SQL spec or not, but it seems very odd. The
queries seem to be converted to lowercase before they ever reach the SQL
engine.
Brian
+
Flash web sites from $149/year w/ hos
Maybe this isn't technically a bug, but I found it strange. With PostgreSQL
7.0.3 and 7.1beta6, I can create a database "FOO", but can only later connect to
it as "foo". I'm not sure if this is a psql thing or a backend thing, or if
it's intended to be this way, but it makes some of my scripts
* Limin Liu <[EMAIL PROTECTED]> [001107 19:11] wrote:
> Hi,
>
> I am new in PostgreSQL and have a simple question:
> Is there any way we can find out which db the current client is working
> with?
>
> In psql, the prompt tells us the current open db, but I may need to
> access that information i
Hi,
I am new in PostgreSQL and have a simple question:
Is there any way we can find out which db the current client is working
with?
In psql, the prompt tells us the current open db, but I may need to
access that information in a C client on the fly with may db opened. I
wonder if this is possi
21 matches
Mail list logo
