Reputation
908
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
4 6
Impact
~38k people reached

Dec
1
comment PostgreSQL Page-level locking
PostgreSQL doesn't have page level locking.
May
7
comment postgresql log queries single database
Yes he was wrong, check the manual: postgresql.org/docs/current/interactive/… This setting can be changed by the superuser at any time for any database.
Feb
16
comment Howto dedicate one cpu core to os in PostgreSQL DB server
Are you sure? A single database connection (a.k.a. single database proces), can only use a single core. That means that no query will ever be able to eat up all CPU's/cores.
Sep
21
comment Get back the Disk space from Postgresql
Stop all processes on that table on a quiet moment and do a VACUUM FULL. Afterwards, you need a REINDEX for this table as well, VACUUM FULL might inflate your indexes. VACUUM FULL will always disturb other processes, that's why you need auto_vacuum to prevent the need for a VACUUM FULL.
Aug
17
comment installing PostGIS PostgreSQL 9.1 on windows
PostgreSQL version 9.1 is still in Beta. If you think the installer is not complete, send a report to the PostgreSQL project.
Aug
10
comment why postgresql doesn't initdb at startup?
This is not a PostgreSQL issue, PostgreSQL doesn't create/maintain the script in init.d for CentOS.
Mar
2
comment pg_restore taking much longer than pg_dump
A 3 to 4 MiB backup file should be restored in a few seconds, not minutes. Even when using older hardware. Did you check wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server for the configuration?
Mar
2
comment pg_restore taking much longer than pg_dump
Additional information: pg_dump doesn't have access to the content of an index. pg_dump uses SELECT statements to get all content of the tables and content of the system tables to create the backup. It's "just" a wrapper around some SELECT statements and some functions to write the results to disk.
Mar
2
comment pg_restore taking much longer than pg_dump
No, the content of the index can't be part of the backup. For a very small database like yours (3-4 MiB), it shouldn't be a problem anyway.
Feb
25
comment Is the community MySQL safe for production use?
Be aware that DDL is never transaction safe in MySQL, unlike PostgreSQL and many other dbms's.
Feb
16
comment any tips for upgrade postgres 8.2 to 8.4?
WHERE dob LIKE '%-09-%' should be rewriten to WHERE EXTRACT(month FROM dob) = 9. Now you can also use an index on the month, to speed things up: CREATE INDEX idx_dob_month ON t (EXTRACT(month FROM dob));
Feb
14
comment PostgreSQL ILIKE doesn't return any data?
Create a test case as simple as possible, a table with just a single record. Do it on both databases and find out what's going on. I guess you're using different content in the table on server B, the SQL looks fine. Altrough I wouldn't use the dollar-quoting approach, just normal quotes ' to stay close to ANSI-SQL.
Feb
10
comment Where is initdb in Ubuntu
initdb is somewhere on your system, PostgreSQL needs it to get started in the first place.
Feb
9
comment ssl on postgres
PostgreSQL version 8.1 is already End Of Life. Consider an upgrade to a newer version, SSL support has also improved in later versions. 9.0 is a good candidate, you are already using the psql client.
Feb
1
comment postgres is unbearably sluggish after a 130MB pg_restore. how to fix?
Can you show us the results from EXPLAIN ANALYZE for a slow query on these tables? And what about configuration settings? work_mem, shared_buffers, maintenance_work_mem and some others, need some tweaking. 130MB is a small database, the whole database should be in RAM.
Jan
28
comment PostgreSQL Left join select VS Normal select
When you have 500-1000 concurrent connections, you need a connectionpool. We have up to 1500 concurrent users working in the application and doing their thing, on a pool of just 100 concurrent connections. Works great, also for queries with many joins. 2GB RAM is a problem, that's not going to give you much performance. For a 1000 concurrent connections, you need as much RAM as you can buy. RAM is cheap.
Jan
27
comment PostgreSQL Left join select VS Normal select
4 tables isn't "many tables", it's almost nothing. Most of our SELECT statements have 10 to 20 joins in them, no problem at all for PostgreSQL. Use EXPLAIN, that's what you need.
Jan
14
comment Is PostgreSQL suited to one OS? Is it better on Linux than Windows?
This ain't a software problem, no developer has ever to worry about his SQL: PostgreSQL uses the samen SQL on Linux as it does on Windows.
Dec
24
comment What are performance limits of a database?
Impossible to anwser, it all depends on your needs. No benchmark did a test using your database nor using your application and hardware.
Dec
9
comment How can I reset the password on a PostgreSQL database on my machine?
See the manual: postgresql.org/docs/current/interactive/auth-pg-hba-conf.html