Dear all,
I am currently experiencing troubles with the performance of my critical's database.
The problem is the time that the postgres takes to perform/return a query. For
example, trying the \d command takes between 4 or 5 seconds. This table is
very big, but I am not asking for the row
Am Mittwoch, 1. September 2004 12:06 schrieb G u i d o B a r o s i o:
> The problem is the time that the postgres takes to perform/return a
> query. For example, trying the \d command takes between 4 or 5
> seconds. This table is very big, but I am not asking for the rows, only
> asking the tabl
The solution appeared as something I didn't know
On the .conf file
Previous situation:
#log_something=false
log_something=true
Worst situation
#log_something=false
#log_something=true
Nice situation
log_something=false
#log_something=true
Ok, the problem was that I assumed that commentin
Hi,
I am using Postgresql 7.4.3 running on RedHat Linux 2.4.7. My Application is
coded in C. I am using libpq functions inorder to connect to the database.
I am using PQsetdbLogin() to connect and PQfinish() to release the database
connection. In my application I have around 15-20 C functions. I
Again me,
To make it easier.
Situation A:
log_something = true
Situation B:
# log_something =
Situation C:
log_something = false
After the pg_ctl reload:
Situation B = Situation A
Situation C <> (Situation A || Situation B)
Is this the expected behavior?
Conclusion:
If you comment a
Hi All,
Anyone good in writing Linux scripting for backup
PostgreSQL. I just required a simple scripts only.
Normally we do the manual ways as following:
In root
root# su postgres
bash# pgdumpall > backup.sql
bash# exit
root#
Im planning to write script.sh for cronjob but not
too sure ab
"Pradeepkumar, Pyatalo (IE10)" <[EMAIL PROTECTED]> writes:
> I am using Postgresql 7.4.3 running on RedHat Linux 2.4.7. My Application is
> coded in C. I am using libpq functions inorder to connect to the database.
> I am using PQsetdbLogin() to connect and PQfinish() to release the database
> con
This issue was resently discussed on hackers. It is a known issue, not very
convinient for the user. Nevertheless it is not fixed in 8.0, but will
perhaps be addressed in the next major release.
(Remembering, it was a non-trivial thing to change.)
Best Regards,
Michael Paesold
G u i d o B a r o s
Thanks for the reply,
Been reading hackers of Aug 2004 and found the threads. It's a common habit to
create two lines on the configuration files, in order to maintain the copy of the
default conf file. I guess this should be the worst scenery for a freshly incoming DBA
trying to put things in
I need some help understanding locales and what the impact upon my
database/application would be.
I am currently running 7.3.4 and have a database with tons of varchar
fields. However, when we query on one of the fields with a like, it
does not use an index. Apparently from the documentation,
Chris Hoover wrote:
> with the locale specifically set to C (initdb --locale=C ...). This
> has fixed the index usage problem, but I don't understand what
> ramifications if any it has on my database. Please help me
> understand what this means to me as the dba.
The sort order will be different.
Would you please be so kind to provide a bit more explanation? How will
the sort differ? Are the any good pages out there that would help me
understand the ramifications?
Thanks,
Chris
Peter Eisentraut wrote:
Chris Hoover wrote:
with the locale specifically set to C (initdb --locale=C ...).
Hello All,
I cannot re-create a database properly.
I did a dump all of one database that runs on production.
I copied the dmp file to dev environment, DROPped the existing database, CREATEd
the database anew and then ran the dump in psql to recreate the database.
The database (and/or db serv
Hello!
Is there any way to see that a postmaster is running with
what configuration? I want to verify if it picked up all the values from postgresql.conf or not. Also I want to know what values it
has taken for the parameters which are commented in my conf file.
Regards,
akshay
hi,
I am having trying to install Postgres 7.4.5, I have gmake 3.76.1 installed.
I have completed following steps:
./configure --prefix=/opt/local --enable-multibyte --enable-unicode
--with-java --without-readline
make
su rootr
make install
adduser postgres
mkdir /opt/local/pgsql
Joseph Sadove <[EMAIL PROTECTED]> writes:
> When I DROP it again and just re- CREATE it, without doing anything, all the
> schemas and objects are there as if I never dropped it.
It sounds to me like you have put a bunch of junk into the template1
database. This was a bad move :-(. What you can
"Akshay Mathur" <[EMAIL PROTECTED]> writes:
> Is there any way to see that a postmaster is running with what
> configuration? I want to verify if it picked up all the values from
> postgresql.conf or not. Also I want to know what values it has taken for
> the parameters which are commented in my co
Seamus Ryan <[EMAIL PROTECTED]> writes:
> Note in the initdb script I altered the call to postgres to turn on debug:
Hmmm
> Any hints on why InitPostgres is not finding database "postgres"?
Because there isn't one --- at that point in the process, only database
template1 will exist.
The po
Hi,
I'm running PostgreSQL 7.4.2, UnixODBC Driver Manager: 03.51.0002.0224
and psqlODBC 7.3.2 on a Red Hat Linux system. I need to understand what
the parameters in the odbc.ini do. In particular what these parameters
do.
Trace
TraceFile
Debug
DebugFile
CommLog
I looked in the 'Notes on the vari
Greetings,
Are there any differences, advantages of running a dump/restore vs
running the following:1)REINDEX all the tables in all the databases,
2)VACUUM FULL ANALYZE on all the databases
Assuming the following
1) the system can be offline.
2) PG version 7.4.x
3) pg_autovacuum running as a dae
Lawrence C,
On Wednesday 01 September 2004 14:20, you went:
> Anyone good in writing Linux scripting for backup
> PostgreSQL. I just required a simple scripts only.
>
> Normally we do the manual ways as following:
>
> In root
>
> root# su - postgres
> bash# pgdumpall > backup.sql
> bash# exit
> ro
For that matter:
echo "1 3 * * * postgres /usr/local/bin/pg_dumpall >
~/backup.sql" >> /etc/crontab
note to remember the two >>'s so you don't obliterate your crontab like
I just did.
:ulp:
-kaolin
tim hall wrote:
Lawrence C,
On Wednesday 01 September 2004 14:20, you went:
Anyone
22 matches
Mail list logo
