Sorry if my terminology is not accurate. But by an instance, I mean a
PostgreSQLinstallation. And I call it an instance (and not a database) not to
confuse itwith the concept of databases (as in databases / schemas). Even when
I'm tryingto clarify the terminology, it's hard due to lack of distin
On 07/25/2016 08:34 AM, Mehran Ziadloo wrote:
I understand that:
1) you like to use postgres as a "bus" to transfer messages between
connected
clients;
2) only one database server is concerned (no redundancy at all);
3) it is the client code (perl, php ...) that send the notification (ie,
notif
On 07/25/2016 11:50 AM, Matthew Musgrove wrote:
One of our instances has been behaving -- oddly. Most queries are
blazing fast. It appears to just be some of the stat views that are slow.
Does anyone have any suggestions on how to:
- see what the statistics collector is doing?
- tell the p
Matthew Musgrove writes:
> One of our instances has been behaving -- oddly. Most queries are blazing
> fast. It appears to just be some of the stat views that are slow.
It sounds like requests for stats updates are not getting through to the
collector. I wonder if your kernel is blocking those
One of our instances has been behaving -- oddly. Most queries are blazing fast.
It appears to just be some of the stat views that are slow.
Queries against the following views are quick: pg_stat_activity,
pg_stat_xact_all_tables, pg_stat_xact_sys_tables, pg_stat_xact_user_tables,
pg_statio_sys_
>Outputs two columns, one polymorphic match and one constant.
Nice.
>I couldn't figure out a way to get the output into columns.
I have had a fair play and am struggling also. Seems like any work around
is going to be too unholy to be worth running.
Thanks for having a crack!
Peter
> I understand that:> 1) you like to use postgres as a "bus" to transfer
> messages between connected> clients;> 2) only one database server is
> concerned (no redundancy at all);> 3) it is the client code (perl, php ...)
> that send the notification (ie,> notifications are not sent by triggers
What is your pg_stat_tmp directory ? Just a random guess, any chances that
someone played with pgstat.stat file ?
Thanks,
Adarsh Sharma
On Mon, Jul 25, 2016 at 8:51 PM, Sameer Kumar
wrote:
>
>
> On Mon, 25 Jul 2016, 10:35 p.m. Adrian Klaver,
> wrote:
>
>> On 07/25/2016 07:28 AM, Sameer Kumar w
On 07/25/2016 08:21 AM, Sameer Kumar wrote:
Don't suppose you still have the logs from that date to see if there is
a clue?
I don't have them on the server. I can fetch them from the archives. Ot
might tke a day or two. Let me get back. Thanks for helping.
Any idea about probable
On Mon, 25 Jul 2016, 10:35 p.m. Adrian Klaver,
wrote:
> On 07/25/2016 07:28 AM, Sameer Kumar wrote:
> >
> >
> > On Mon, 25 Jul 2016, 10:10 p.m. Adrian Klaver,
> > mailto:adrian.kla...@aklaver.com>> wrote:
> >
> > On 07/24/2016 09:58 PM, Sameer Kumar wrote:
> > > Hi,
> > >
> > > I
> I understand that:> 1) you like to use postgres as a "bus" to transfer
> messages between connected> clients;> 2) only one database server is
> concerned (no redundancy at all);> 3) it is the client code (perl, php ...)
> that send the notification (ie,> notifications are not sent by triggers
On 07/25/2016 07:28 AM, Sameer Kumar wrote:
On Mon, 25 Jul 2016, 10:10 p.m. Adrian Klaver,
mailto:adrian.kla...@aklaver.com>> wrote:
On 07/24/2016 09:58 PM, Sameer Kumar wrote:
> Hi,
>
> I have PostgreSQL v9.4.4 running in my environment. It has been up for
> over 2 years n
On Mon, 25 Jul 2016, 10:10 p.m. Adrian Klaver,
wrote:
> On 07/24/2016 09:58 PM, Sameer Kumar wrote:
> > Hi,
> >
> > I have PostgreSQL v9.4.4 running in my environment. It has been up for
> > over 2 years now. I noticed that suddenly the statistics have been reset
> > and all the stat tables/colum
On 07/24/2016 09:58 PM, Sameer Kumar wrote:
Hi,
I have PostgreSQL v9.4.4 running in my environment. It has been up for
over 2 years now. I noticed that suddenly the statistics have been reset
and all the stat tables/columns got restarted from.
Any of these happen?:
https://www.postgresql.org/
On Mon, Jul 25, 2016 at 6:14 AM, Peter Devoy wrote:
>
> BEGIN
> RETURN QUERY
> EXECUTE
> format(
> '
> SELECT
> %1$I.*,
> dist_query.distance AS appended_distance,
> dist_query.centroid AS appended_centroid
> FROM %1$I
>
@David, thanks for the tip.
>Providing a concrete example might help.
My use case is a database with a large number of spatial tables. I
have written a spatial search function which, given an arbitrary table
extended with PostGIS, will search for records in that table whose
geometries are within
16 matches
Mail list logo