On Wednesday 12 July 2006 11:15, hector ramiro garcia cantu wrote:
> unsubscribe pgsql-admin
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
= select version();
version
---
PostgreSQL 8.1.4 on sparc-sun-solaris2.9, compiled by GCC gcc (GCC) 3.4.2
(1 row)
--
---
Admins; we have a few corrupt objects after a disk array event
yesterday. One of the problems was resolved by simply dropping and
reloading a table from backup.
I have another table however that's going to b a stinker. I can't
drop, rename or re-schema it.
We have 2 tabs with same name in diffe
Ah, I've actually run into this problem before. Seems
I'd forgotten to explicitly set the NLS_LANG parameter
in the Ora2Pg script. Once I set it to
AMERICAN_AMERICA.UTF8 it seems to work just dandy.
--- Andy Shellam <[EMAIL PROTECTED]> wrote:
> Is your database and client encoding set to UTF-8?
On 7/14/06, Spiegelberg, Greg <[EMAIL PROTECTED]> wrote:
We've also wrapped the psql command with our own script which takes adatabase name as a parameter, determines what IP & port to connect toand also determines the version of postgres running so the proper psql
client is invoked. I don't know
Is your database and client encoding set to UTF-8?
That's about all I can think of.
Chaun Keating wrote:
Hello, I have gotten Ora2pg to work fairly well for
me, but I am having an issue where mutibyte characters
are being substituted with replacement characters on
export from Oracle.
I used
Hello, I have gotten Ora2pg to work fairly well for
me, but I am having an issue where mutibyte characters
are being substituted with replacement characters on
export from Oracle.
I used both the output to a file and the direct import
to a PG database and see a bunch of question marks
instead of m
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 7/14/06, Donald Fraser <[EMAIL PROTECTED]> wrote:
Is there a mechanism for attaching a trigger function, or the likes, to be
activated when a user logs into the PostgreSQL database?
I'm looking for a means of performing additional house keeping tasks when a
user logs in.
A patch currently ex
We have done this here and it works well. In our case we have two
different rev's of PostgreSQL which we install as /path/to/pgsql-7.4.6
and /path/to/pgsql-8.1.3 but reference using links /path/to/pgsql-7.4
and /path/to/pgsql-8.1. Reason is you don't want to muck with your path
every time you upg
Is there a mechanism for attaching a trigger function, or
the likes, to be activated when a user logs into the PostgreSQL
database?
I'm looking for a means of performing additional house keeping
tasks when a user logs in.
Regards
Donald Fraser
Am Freitag, 14. Juli 2006 08:36 schrieb kitaeda:
> I want to install two postgresqls in the same machine.
> How can I do so?
> What do I have to specific configure options?
>
You have to have them in different locations obviously, so you might
use a different --prefix=... for both on configure. And
I want to install two postgresqls in the same machine.
How can I do so?
What do I have to specific configure options?
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
13 matches
Mail list logo
