Hi List,
I want to create a new table with the data and constraints as it is from
existing table. I could create a new table with the existing table data
as " create table test2 as select * from test1; ". Here the constraints
are not copying. Can any one please show me the way.
Regards,
Amit jain wrote:
Hello All,
We are using postgresql version 8.1 and our database size is 7gb. Ram Size
is 2 GB.
while trying to take backup through pg_dump i am getting following error.
oka97: pg_dump amtdb > amtdb.out
pg_dump: ERROR: invalid memory alloc request size 4294967293
pg_dump: SQ
I have a large table with about 2 million rows and it will keep growing...
I need to do update/inserts, and select as well.
An index will speed up the select, but it will slow down the updates.
Are all Postgres indexes ordered? i.e., with every update, the index pages will
have to be physically
I have a large table with about 2 million rows and it will keep growing...
I need to do update/inserts, and select as well.
An index will speed up the select, but it will slow down the updates.
Are all Postgres indexes ordered? i.e., with every update, the index
pages will have to be physica
The only setting I see is an account expire, but I do not want to lock
the people out of the accounts.
I just want to force each user to set a new password on minimum
intervals.
Does Postgres have a way to require users to change their passwords
every 90 days for example, with out locking the acco
Blakely, Jerel (Mission Systems) wrote:
The only setting I see is an account expire, but I do not want to lock
the people out of the accounts.
I just want to force each user to set a new password on minimum
intervals.
Does Postgres have a way to require users to change their passwords
every
Hello,
I posted yesterday about a corrupt index. I'm continuing to
experience problems. I know that part of my problem is that the
databases have not been vacuumed as they should have been. I've
tried to vacuum them but it's not working. The message I'm getting
is as follows:
vacuum
On Fri, 2008-05-23 at 13:54 -0400, Carol Walter wrote:
> Hello,
> vacuumdb: vacuuming database "km"
> NOTICE: number of page slots needed (2275712) exceeds max_fsm_pages
> (20)
> HINT: Consider increasing the configuration parameter
> "max_fsm_pages" to a value over 2275712.
>
> The p
Carol Walter wrote:
vacuumdb: vacuuming database "km"
NOTICE: number of page slots needed (2275712) exceeds max_fsm_pages
(20)
HINT: Consider increasing the configuration parameter "max_fsm_pages"
to a value over 2275712.
The problem is I've found the max_fsm_pages parameter in the
po
Oh, yes. I have restarted it several times - or at least I thought
that I did. Actually, it's not stopping. I grepped for "post" after
I did the stop and it is still running. I really don't like the idea
of issuing the kill command on the database processes. Is there
another option?
On Fri, 2008-05-23 at 14:35 -0400, Carol Walter wrote:
> Oh, yes. I have restarted it several times - or at least I thought
> that I did. Actually, it's not stopping. I grepped for "post" after
> I did the stop and it is still running. I really don't like the idea
> of issuing the kill
Does this do an orderly, safe stop? Also do I then bring it back up
with the usual command?
Thanks,
Carol
On May 23, 2008, at 2:39 PM, Joshua D. Drake wrote:
On Fri, 2008-05-23 at 14:35 -0400, Carol Walter wrote:
Oh, yes. I have restarted it several times - or at least I thought
that I
>>> Carol Walter <[EMAIL PROTECTED]> wrote:
> On May 23, 2008, at 2:39 PM, Joshua D. Drake wrote:
>>
>> pg_ctl -D /path/to/data/dir -m fast stop
>>
> Does this do an orderly, safe stop? Also do I then bring it back up
> with the usual command?
"Three different shutdown methods can be selected
Jeff,
Thank you very much. I didn't know about this command. There are
lots of times this would have saved me looking it up in my
documentation. I've got a couple of different instances of postgres
running and I always have to check the docs to find out where my
config file is.
Well,
On Fri, May 23, 2008 at 1:08 PM, Carol Walter <[EMAIL PROTECTED]> wrote:
> Jeff,
>
> Thank you very much. I didn't know about this command. There are lots of
> times this would have saved me looking it up in my documentation. I've got
> a couple of different instances of postgres running and I a
I ran into the 1600 column upper bound in a table and I am trying to
assess if I can work around the limit or if I am in need of a re-design
of my application. All the documentation on the site that I have seen
(CREATE TABLE and postgresql.org/about/) says that 1600 is the limit, I
looked in h
Hello
I have a small application with apache and fastcgi
I use valgrind to debug my app.
see the apache log below (the app run fine, but it's very strange)
This is the call of :
pConn = PQconnectdb(connInfo);
==20793== Thread 3:
==20793== Invalid read of size 8
==20793==at 0x4015B24: (with
Hi
I have noticed something relating to this file that I am slightly worried
about. If you open the pgpass.conf file with Notepad it displays the full
contents in open text - including the administrator name and password.
Is this something that other people have come across and has
protecti
Mike Weber <[EMAIL PROTECTED]> writes:
> I ran into the 1600 column upper bound in a table and I am trying to
> assess if I can work around the limit or if I am in need of a re-design
> of my application.
You need to redesign. The 1600 limit has some slop (intentionally)
but not a lot of slop -
Hi, Again.
I tried this and got the same message. It is as follows:
-bash-3.00$ /opt/csw/postgresql/bin/pg_ctl -D /dbpdisk/postgres/
prod_823 -m fas
t stop
pg_ctl: PID file "/dbpdisk/postgres/prod_823/postmaster.pid" does not
exist
Is server running?
Are there other ideas?
Carol
This is
Carol Walter wrote:
Hi, Again.
I tried this and got the same message. It is as follows:
-bash-3.00$ /opt/csw/postgresql/bin/pg_ctl -D
/dbpdisk/postgres/prod_823 -m fas
t stop
pg_ctl: PID file "/dbpdisk/postgres/prod_823/postmaster.pid" does not
exist
Is server running?
Are there other ide
Hi ,
I have tried to taken backup while no one is connected. Should i change my
> RAM and then check it. Version are same of pg_dump and database version 8.1.
Yes try that . Though I dont think thats going to help. Just checking are
you using AMD server any chance .
Please provide complete con
Hi, Jeff,
Here's the output from the command.
-bash-3.00$ ps -ef | grep post
postgres 9631 9629 0 Sep 24 ? 30:28 /opt/csw/
postgresql/bin/sparcv8/postgres -D /dbpdisk/postgres/prod_823
postgres 9633 9629 0 Sep 24 ? 96:31 /opt/csw/
postgresql/bin/sparcv8/postgres -
Carol Walter wrote:
-bash-3.00$ ps -ef | grep post
postgres 9631 9629 0 Sep 24 ? 30:28
/opt/csw/postgresql/bin/sparcv8/postgres -D /dbpdisk/postgres/prod_823
postgres 9633 9629 0 Sep 24 ? 96:31
/opt/csw/postgresql/bin/sparcv8/postgres -D /dbpdisk/postgres/prod_82
24 matches
Mail list logo
