[GENERAL] What can we do to create windows 7 boot disk

Maybe one day your windows 7 can't boot unexpectedly and you don't know what to do. Then a solution comes up by create a windows boot disk. If the problem occurs to you,take it easy and read the solutions below which will teach you how to burn a windows 7 boot disk

Re: [GENERAL] Error: absolute path not allowed

I found what pg_read_file didn't like. With the help of enterprisedb support which gave me the steps to see what was wrong 1. set log_min_duration_statement = 0 in postgresql.conf: This will log all statements 2. select pg_reload_conf(); reloads the parameters 3. Wait until the error message come

Re: [GENERAL] [postgis-users] Query with LIMIT but as random result set?

Stefan Keller wrote: > "... ORDER BY random() LIMIT 10;" works ok. > > But with the following option it gets more tricky assume: >> And as an option the (limited) resultset should be spatially >> distributed (not clustered). > > I'm thinking about some radial spatial distribution function. So,

Re: [GENERAL] When to run Vacuum in postgres 9.0.4

[resending after completion -- the prior send was accidental] Anjali Arora wrote: > I have a large dataset and I have crawled it two and three times; > hence reltuples has increased. So I need some way to find out > vacuum is needed on the system. > > Please help me in finding out some paramete

Re: [GENERAL] Identifier gets truncated

On Thu, Jan 10, 2013 at 03:36:32PM +0100, Peter Kroon wrote: > When an identifier has more then 63 chars it gets truncated. > This is fine. > However PostgreSQL fails to notice that it might truncate to an identifier > which already exist. > Does PostgreSQL got a setting that will never create a du

Re: [GENERAL] When to run Vacuum in postgres 9.0.4

Anjali Arora wrote: > I have a large dataset and I have crawled it two and three times; hence > reltuples has increased. So I need some way to find out vacuum is needed on > the system. > > Please help me in finding out some parameter or statistics which will tell me > vacuum is required on t

Re: [GENERAL] Bug: dblink_send_query not work on 9.2?

Thank you! It's now works perfectly! -- View this message in context: http://postgresql.1045698.n5.nabble.com/Bug-dblink-send-query-not-work-on-9-2-tp5739365p5739526.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-gene

Re: [GENERAL] Error: absolute path not allowed

I added the values to log_line_prefix but this still doesn't give me anymore info on why I'm getting the error log_line_prefix = '%t [%p]: [%1-1] db=%d, user=%u, client=%h ' 2013-01-10 07:42:03 MST [8555]: [-1] db=postgres, user=postgres, client=10.11.0.200 ERROR: absolute path not allowed 2013-

Re: [GENERAL] Error: absolute path not allowed

I did some more debugging and found that I'm only getting the errors on the databases that is being monitored by Postgres Enterprise Manager. I Will have to contact EnterpriseDB support -- View this message in context: http://postgresql.1045698.n5.nabble.com/Error-absolute-path-not-allowed-tp57

[GENERAL] data corruption when using base backups generated from hot standby

Greetings, I'm running postgres-9.2.2 in a Linux-x86_64 cluster with 1 master and several hot standby servers. Since upgrading to 9.2.2 from 9.1.x a few months ago, I switched from generating a base backup on the master, to generating it on a dedicated slave/standby (to reduce the load on the mast

Re: [GENERAL] [Solved] Corrupt indexes on slave when using pg_bulkload on master

On Thu, Jan 10, 2013 at 6:51 AM, Tom Lane wrote: > James Cowell writes: >> But pg_bulkload only puts the index updates into WAL if you also have >> >> archive_mode = on >> >> I guess it needs to test wal_level rather than archive mode now? It looks >> like changes to the project have been minim

[GENERAL] Identifier gets truncated

When an identifier has more then 63 chars it gets truncated. This is fine. However PostgreSQL fails to notice that it might truncate to an identifier which already exist. Does PostgreSQL got a setting that will never create a duplicate identifier? really_long_name_table_A -> really_long_na really_

Re: [GENERAL] query by partial timestamp

On Wednesday, January 9, 2013 at 04:42, Michael Nolan wrote: On 1/8/13, Gavan Schneider wrote: 2. SELECT ... WHERE '2011-01-01'::TIMESTAMP <= col_of_type_timestamp ANDcol_of_type_timestamp <= '2011-12-31'::TIMESTAMP; This won't quite work, because '2011-12-31'::