this out.
Best Regards
Dave
From: Day, David
Sent: Wednesday, February 18, 2015 8:07 AM
To: 'Guy Helmer'
Cc: 'pgsql-general@postgresql.org'
Subject: RE: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
Update/Information sharing: ( FreeBSD 10.0 (amd
Situation
I have a co-developer installing a new Virtual Machine and encountering a
postgres error during the installation.
One of our SQL patch files is failing unexpectedly.
The patch is attempting to add columns to a table, The table involved
currently has only 2 columns,
Interactively I
select count(*) from pg_attribute where
attrelid='log.conference_history'::regclass and attnum > 0 and attisdropped;
count
---
1598
From: Pavel Stehule [mailto:pavel.steh...@gmail.com]
Sent: Monday, April 13, 2015 12:06 PM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject
Hi,
Postgres version 9.3.9
What is wrong with my usage of the plpgsql "select into" concept
I have a function to look into a calendar table to find the first and
Last weekend date of a month.
In this simplified concept function I end up with a NULL for first or last
weekend variable.
cr
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Monday, June 29, 2015 4:03 PM
To: Day, David; pgsql-general@postgresql.org
Subject: Re: [GENERAL] plpgsql question: select into multiple variables ?
On 06/29/2015 12:07 PM, Day, David wrote:
>
problem was in casts
that I was using were confusing the parser and were un-necessary.
Appreciate your thought and effort.
Regards
Dave
From: Yasin Sari [mailto:yasinsar...@googlemail.com]
Sent: Tuesday, June 30, 2015 3:26 AM
To: Day, David
Subject: Re: [GENERAL] plpgsql question: select into
I have a development site ( FreeBSD 10.1 and Postgres 9.3 ) where I can
connect to the database via psql or pgadminIII both locally and remotely.
However, all of the local apps ( 3 different ones ) that would connect to it
are failing to connect.
I see no error events in the messages/postgres
st all all 192.168.32.0/19 trust
I don’t believe this to be a postgres problem, but you don’t know what you
don’t know.
From: David G. Johnston [mailto:david.g.johns...@gmail.com]
Sent: Friday, October 23, 2015 10:36 AM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERA
.
After seeing that I able to run down the installation flaws.
Thanks very much to all for your suggestions on this matter.
Regards
Dave
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Friday, October 23, 2015 12:49 PM
To: Day, David
Cc: pgsql-general@postgresql.org
Hi,
There seems to be an unbounded growth of memory usage by the backend postgres
process representing a "permanent" session in our system.
The size/res values retrieved by running the "top" utility seem to exceed the
amount I would expect given the mem and buf tuning parameters of the
pos
14, 2016 11:22 AM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Server side backend permanent session memory usage ?
"Day, David" writes:
> There seems to be an unbounded growth of memory usage by the backend
> postgres process representing a "permanent&
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Wednesday, July 27, 2016 4:50 PM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Server side backend permanent session memory usage ?
"Day, David" writes:
> We have a server
Hi,
One of my co-workers came out of a NIST cyber-security type meeting today and
asked me to delve into postgres and zeroization.
I am casually aware of mvcc issues and vacuuming
I believe the concern, based on my current understanding of postgres inner
workings, is that when a dead tup
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Wednesday, November 18, 2015 3:47 PM
To: Day, David; pgsql-general@postgresql.org
Subject: Re: [GENERAL] postgres zeroization of dead tuples ? i.e scrubbing dead
tuples with sensitive data.
On 11/18/2015 11
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Wednesday, November 18, 2015 4:05 PM
To: Day, David; pgsql-general@postgresql.org
Subject: Re: [GENERAL] postgres zeroization of dead tuples ? i.e scrubbing dead
tuples with sensitive data.
On 11/18/2015
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Thursday, November 19, 2015 10:32 AM
To: Day, David; pgsql-general@postgresql.org
Subject: Re: [GENERAL] postgres zeroization of dead tuples ? i.e scrubbing dead
tuples with sensitive data.
On 11/19/2015
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Thursday, November 19, 2015 11:06 AM
To: Day, David; pgsql-general@postgresql.org
Subject: Re: [GENERAL] postgres zeroization of dead tuples ? i.e scrubbing dead
tuples with sensitive data.
On 11/19/2015
Hello,
Understanding postgresql memory usage ?
While traffic loading our application that uses a postgres 9.3.11 database
instance, we observe higher RAM usage then expected. The system bogs down as
free memory decreases to minimal values. The most RAM usage seems to be with
postgres backe
ave too many objects or queries planned you might take up too much ram.
If this is indeed your situation, you might benefit from shorter lived
connections.
Regards,
- Jony
On Fri, Apr 15, 2016 at 12:14 AM, Day, David
mailto:d...@redcom.com>> wrote:
Hello,
Understanding postgresql mem
Hoping for a teachable moment :+)
With options enabled to log statement execution times in the postgres log
file I observe:
2014-09-02T12:47:38.107808-04:00 alabama local0 info postgres[37874]: [702-1]
user=ace_db_client,db=ace_db LOG: duration: 0.040 ms statement: BEGIN
2014-09-02T12:47:38
If I have a select statement where I am formatting both a duration ( interval
data type ) and timestamp ( timestamp with tz datatype ) I am getting an odd
behavior.
Note the extra characters following the seconds in the last_update column.
ace_db=# select port_id,
to_char(ppa.term_
We are developing on and running Postgres 9.3.5 on FreeBsd 10.0-p12.
We have been experiencing a intermittent postgres core dump which
Seems primarily to be associated with the the 2 functions below.
The area of interest is based on the content of the postgres log file which
often indicates
Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Wednesday, December 03, 2014 3:57 PM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
"Day, David" writes:
> We are developing on and runnin
It has been some time since we have seen this problem.
See earlier message on this subject/thread for the suspect plperl function
executing
at the time of the core.
Someone on our development team suggested it might relate to some build
options of perl.
In particular MULTIPLICITY or THREADS
segmentation fault puzzling.
Regards
Dave
From: Alex Hunsaker [mailto:bada...@gmail.com]
Sent: Thursday, January 29, 2015 12:58 AM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
On Wed, Jan 28, 2015 at 1:23
infrequency of the segmentation fault puzzling.
Regards
Dave
From: Alex Hunsaker [mailto:bada...@gmail.com]
Sent: Thursday, January 29, 2015 12:58 AM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
On Wed
Thanks for the inputs, I’ll attempt to apply it and will update when I have
some new information.
Thanks
Dave
From: Alex Hunsaker [mailto:bada...@gmail.com]
Sent: Thursday, January 29, 2015 3:30 PM
To: Day, David
Cc: pgsql-general@postgresql.org; Tom Lane
Subject: Re: [GENERAL] segmentation
segmentation fault
Thanks for your assistance on this matter.
Dave
From: Alex Hunsaker [mailto:bada...@gmail.com]
Sent: Thursday, January 29, 2015 6:10 PM
To: Day, David
Cc: pgsql-general@postgresql.org; Tom Lane
Subject: Re: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
On
Update/Information sharing on my pursuit of segmentation faults
FreeBSD 10.0-RELEASE-p12 amd64
Postgres version 9.3.5
Below are three postgres core files generated from two different machine (
Georgia and Alabama ) on Feb 11.
These cores would not be caused from an environment update issue th
couple of suggestions to follow up on.
I’ll keep the thread updated.
Thanks, a good start to my Friday the 13th.
Regards
Dave Day
From: Guy Helmer [mailto:ghel...@palisadesystems.com]
Sent: Thursday, February 12, 2015 6:19 PM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re
13th.
Regards
Dave Day
From: Guy Helmer [mailto:ghel...@palisadesystems.com]
Sent: Thursday, February 12, 2015 6:19 PM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
On Feb 12, 2015, at 3:21 PM, Day
Hi,
I am working on a plpgsql function that is not acting as I would hope.
I am working with the Postgres 9.3 beta load and would like to
solicit some feedback.
Looking at the outermost for loop of the function below, If I run this CTE
query from the psql command line
I am returned what I exp
rs -
END LOOP; -- drow
END LOOP; -- drow
END
$BODY$
LANGUAGE plpgsql VOLATILE
COST 100;
select admin.activate_translate_user1(1);
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Friday, August 09, 2013 10:20 AM
To: Day, David
Cc
wsrow."pattern_match", wsrow."screen_class",
wsrow."term_mode",
wsrow."trans_result", wsrow."port_id", wsrow."tag_id",
wsrow."cause__q850", wsrow."cause__redcom",
wsrow.
, 2013 6:14 PM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] plpgsql FOR LOOP CTE problem ?
"Day, David" writes:
> A complete self contained test case: example of the problem with my FOR LOOP
> using a COMMON table expression.
Ah, I see the problem.
I have needs to do selective schema or table restorations and the pg_restore
utility seems to have hooks for this, yet seems deficient for this type of
problem.
It appears that I have to develop a custom script to do what I think would
be a standard kind of restorations.
---
Given: Postgres 9.3
ke to own
the firearm :+)
Regards
Dave Day
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@gmail.com]
Sent: Thursday, January 09, 2014 3:47 PM
To: Day, David; pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_restore - selective restore use cases. HINT use DROP
CA
assistance.
Dave
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@gmail.com]
Sent: Thursday, January 09, 2014 6:09 PM
To: Day, David; pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_restore - selective restore use cases. HINT use DROP
CASCADE
On 01/09/2014 01:51 PM,
Hi,
This is sort of a continuation of = problems I was working on last week
with selective restorations of an archive file at the schema or table level. (
V9.3)
Given that I dumped the entire database ( pg_dump -Fc my_db -f archive_file )
When I pg_restore an entire schema ( -n ) everything
duplicated data.
This ( -a -c ) would be a nice combination of pg_restore as pg_dump as I recall
does not allow for that combination.
Rgds
Dave
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@gmail.com]
Sent: Monday, January 13, 2014 7:36 PM
To: Day, David; pgs
advise.
Thanks
Dave
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@gmail.com]
Sent: Tuesday, January 14, 2014 10:33 AM
To: Day, David; pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_restore - table restoration
On 01/14/2014 06:06 AM, Day, David wrote:
> Adr
Hi,
Should I be able to run two syslog facilities simultaneously ( postgres local0,
and a trigger function to local3 ) successfully ?
I have postgresql 9.3.1exit running on freebsd and sending errors to
"syslog_facility= local0".
That works fine.
I have created an insert trigger on one o
PM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] syslog facilites and postgres ?
"Day, David" writes:
> Should I be able to run two syslog facilities simultaneously ( postgres
> local0, and a trigger function to local3 ) successfully ?
Probably not
Hi,
I have an embedded application retrieving data from a postgres database using
the ECPG client interface. One process acts as an intermediary for other
tasks for r/w operations.
When the the pg interface task retrieves a row into a sql descriptor and
inspects the column types for a decl
Hi,
I took a patch that was available under 8.0.4 for Avahi zeroconfig and adpted
it to 9.0.3.
Though publication of the service type _postgresql._tcp is successful. When I
shutdown the
Postgres server the advertised service is not removed from mDNS and is visible
though not resolvable for a
Hi,
If I am retrieving row(s) into a sql descriptor in ECPG, and my last row
column is of type timestamp, then I I will consistently receive a segmentation
fault as shown below. If I redefine the table so that the timestamp field is
not the last field of the table row, the routine runs suc
46 matches
Mail list logo
