Re: [GENERAL] [ADMIN] How to drop stats on table

the actual issue is, when 1. temp table is created with rows 2. stats/analyze on table (tmp1) 3. table dropped (tmp1) but in stats related catalog tables a blot is created In this scenario, thousands of temp tables created per day, blots are increasing and stats related tables are growing to 10'

Re: [GENERAL] postgres zeroization of dead tuples ? i.e scrubbing dead tuples with sensitive data.

On 11/19/15 1:12 PM, Adrian Klaver wrote: >Our app is doing the authentication based on the sensitive >information retrieved from postgres tables. >Our app zeros out its associated memory to the process when it is done >with it. The developer was concerned about the >breadcrumbs left in pos

Re: [GENERAL] duplicate key errors in log file

On 11/18/15 2:42 PM, Jeff Janes wrote: But he already knows it has race conditions. That is why he included retry logic, to deal with those conditions. From the sounds of it there's no retry loop, which means there's still a race condition (data is deleted after insert fails but before update

Re: [GENERAL] controlling memory management with regard to a specific query (or groups of connections)

On Wed, Nov 18, 2015 at 5:10 PM, Jonathan Vanasco wrote: > As a temporary fix I need to write some uploaded image files to PostgreSQL > until a task server can read/process/delete them. > > The problem I've run into (via server load tests that model our production > environment), is that these r

Re: [GENERAL] What could cause CREATE TEMP... "could not read block" error?

On 11/20/2015 07:26 AM, Chris Richards wrote: Adrian is correct. This worked by itself whereas using it in the creation of the temporary table failed. mdb-> SELECT pq.* FROM policyqueue AS pq mdb-> JOIN seed_progress AS sp ON pq.id =sp.polidx; I checked the query Albe suggested;

Re: [GENERAL] What could cause CREATE TEMP... "could not read block" error?

Adrian is correct. This worked by itself whereas using it in the creation of the temporary table failed. mdb-> SELECT pq.* FROM policyqueue AS pq mdb-> JOIN seed_progress AS sp ON pq.id=sp.polidx; I checked the query Albe suggested; there were two `relfilenode`s (11936 and 11937) that exhibited t

Re: [GENERAL] What could cause CREATE TEMP... "could not read block" error?

On 11/18/2015 04:31 PM, Chris Richards wrote: Howdy. I have two tables that I'm joining together and using the result to create a temporary table. Performing the join operation works fine; it produces 0 rows (as expected). If I prepend "CREATE TEMP tmp_policyqueue AS" to the SELECT then it genera

Re: [GENERAL] What could cause CREATE TEMP... "could not read block" error?

On 11/20/2015 06:18 AM, Albe Laurenz wrote: Chris Richards wrote: Howdy. I have two tables that I'm joining together and using the result to create a temporary table. Performing the join operation works fine; it produces 0 rows (as expected). If I prepend "CREATE TEMP tmp_policyqueue AS" to th

Re: [GENERAL] What could cause CREATE TEMP... "could not read block" error?

Chris Richards wrote: > Howdy. I have two tables that I'm joining together and using the result to > create a temporary table. > Performing the join operation works fine; it produces 0 rows (as expected). > If I prepend "CREATE TEMP > tmp_policyqueue AS" to the SELECT then it generates this error

Re: [GENERAL] controlling memory management with regard to a specific query (or groups of connections)

Thanks. Unfortunately, this is in a clustered environment. NFS and other shared drive systems won't scale well. I'd need to run a service that can serve/delete the local files, which is why I'm just stashing it in Postgres for now. > On Nov 19, 2015, at 2:26 AM, Roxanne Reid-Bennett wrot

[GENERAL] What could cause CREATE TEMP... "could not read block" error?

Howdy. I have two tables that I'm joining together and using the result to create a temporary table. Performing the join operation works fine; it produces 0 rows (as expected). If I prepend "CREATE TEMP tmp_policyqueue AS" to the SELECT then it generates this error: ERROR: could not read block 39

Re: [GENERAL] [ADMIN] How to drop stats on table

Sridhar N Bamandlapally wrote: > is there any feature available in postgres to drop stats on table? What about DELETE FROM pg_catalog.pg_statistic WHERE starelid = Yours, Laurenz Albe -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: h

Re: [GENERAL] How to drop stats on table

pg_stat_reset_single_table_counters(oid) ? Best Regards, Alexander Shereshevsky On Fri, Nov 20, 2015 at 1:54 PM, Sridhar N Bamandlapally < sridhar@gmail.com> wrote: > Hi > > is there any feature available in postgres to drop stats on table? > > thanks > Sridhar > > >

[GENERAL] How to drop stats on table

Hi is there any feature available in postgres to drop stats on table? thanks Sridhar

Re: [GENERAL] BDR and Backup and Recovery

On 19 November 2015 at 00:54, Will McCormick wrote: > The below is from the 0.9.3 BDR documentation: > > "Because logical replication is only supported in streaming mode (rather > than WAL archiving) it isn't suitable for point-in-time recovery. Logical > replication may be used in conjunction w

Re: [GENERAL] Fetching from psql procedures

2015-11-20 9:14 GMT+01:00 Marc Mamin : > >> Hi, > >> > >> I'm looking for a way to build large xml documents based on a set of > tables, hence using recursive queries. > >> > >> > >> something like: > >> > >> FOR rec1 IN ... > >> FOR rec2 IN ... > >> > >> RETURN QUERY select '> > >>

Re: [GENERAL] Fetching from psql procedures

>> Hi, >> >> I'm looking for a way to build large xml documents based on a set of tables, >> hence using recursive queries. >> >> >> something like: >> >> FOR rec1 IN ... >> FOR rec2 IN ... >> >> RETURN QUERY select '> >> FOR rec3 IN ... >> >> RETURN QUERY select