Kris Deugau <[EMAIL PROTECTED]> writes:
> Failing that, a diagnostic poke to the head to tell me where in this
> config I should put entries that refer to both local socket connections
> and remote TCP/IP connections for one specific database that I want MD5
> (or crypt, for the old 6.x client :
In particular, something quite a bit more verbose than the offical docs
on www.postgresql.org/docs (which are good, but not quite detailed
enough for me to unravel which entry in one particular pg_hba.conf is
taking precedence, and how to add several new entries that won't break
anything else).
On Sat, Feb 25, 2006 at 09:22:31PM +0800, Vincent Chen wrote:
>
> Hi, all
>
> I have a postgresql 7.4 running on mandriva linux 10.1 with 512M RAM & AMD
> 2000+ CPU. I increased system share memory to 128M, buffer to 64M, sort memory
> to 32M. A single query do finish much faster. Now I need to a
On Wed, Mar 01, 2006 at 10:23:41AM -0500, Tom Lane wrote:
> Ashley Moran <[EMAIL PROTECTED]> writes:
> > BEGIN WORK;
> > DELETE FROM X; COPY X ...; REINDEX TABLE X;
> > DELETE FROM Y; COPY Y ...; REINDEX TABLE Y;
> > DELETE FROM Z; COPY Z ...; REINDEX TABLE Z;
> > COMMIT;
>
> Why don't you use TRU
This is likely because transactions have been rolled back due to the
shutdown. Sequences operate *outside* of transaction space - operations
on a sequence will not be rolled back from a transaction, and a commit
has no effect. There is probably a better way to put that. However, they
should not be
On Wed, Mar 01, 2006 at 11:03:12AM -0500, Tom Lane wrote:
> "sandhya" <[EMAIL PROTECTED]> writes:
> > But lo_open is returning -1(-ve value).
>
> Are you sure that's where it's failing? The fragment you showed looks
> fine as far as it goes. The most likely bet is you forgot to wrap it in
> a
"sandhya" <[EMAIL PROTECTED]> writes:
> But lo_open is returning -1(-ve value).
Are you sure that's where it's failing? The fragment you showed looks
fine as far as it goes. The most likely bet is you forgot to wrap it in
a transaction (BEGIN/COMMIT commands), but that would result in a
failur
On Wed, Mar 01, 2006 at 05:48:51PM +0530, sandhya wrote:
> Is it possible to use lo_open after creating the object while
> the application is running?
Yes, but that's off-topic for pgsql-admin. Try pgsql-interfaces
or pgsql-general.
--
Michael Fuhr
---(end of broadcast)
Ashley Moran <[EMAIL PROTECTED]> writes:
> BEGIN WORK;
> DELETE FROM X; COPY X ...; REINDEX TABLE X;
> DELETE FROM Y; COPY Y ...; REINDEX TABLE Y;
> DELETE FROM Z; COPY Z ...; REINDEX TABLE Z;
> COMMIT;
Why don't you use TRUNCATE? Why do you think you need REINDEX at all?
If you do need it, you'
Is it possible to use lo_open after creating the object while
the application is running?
Hi,
In my application i need to create a file dynamically and load it into
DB.
So.I have created one object at run time .and trying to open
it inorder to write the content into it.
Hi,
In my application i need to create a file dynamically and load it into
DB.
So.I have created one object at run time .and trying to open
it inorder to write the content into it.
But lo_open is returning -1(-ve
value).
where i am doing mistake pls tell me.
lobjId = lo_creat(c
Hi,
In my application i need to create a file dynamically and load it into
DB.
So.I have created one object at run time .and trying to open
it inorder to write the content into it.
But lo_open is returning -1(-ve
value).
where i am doing mistake pls tell me.
lobjId = lo_creat(conn
In your pg_hba.conf file, you could only allow users to access their own
databases, so if they try and login with another database, it fails.
e..g
hostdb1 user1 0.0.0.0/0 md5
hostdb1 user2 0.0.0.0/0 md5
hostdb1 user3
Have you also changed your pg_ident.conf to map the user gowri to a
database user, and does that database user exist in pgSQL?
By default 127.0.0.1 is set up as trust authentication, so if you
haven't changed this, it will always let you through no matter what
username/password you give.
Andy
Use the pg_dump utility in postgresql.
1. to export the database data use .
/usr/local/pgsql/bin/pg_dump [database_name] > filename.dat
2. to export only the schema of the database ./usr/local/pgsql/bin/pg_dump -s [database_name] > schema_filename.sql
NOTE:
/usr/local/pgsql/bin/pg_dump --help
15 matches
Mail list logo
