by Devrim Gunduz and Jeff Frost. Adding them to
the Cc list.
Could you show us the copy/paste of your yum install output?
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Nov 19, 2013, at 4:05 PM, Andres Freund and...@2ndquadrant.com wrote:
Hi,
On 2013-11-19 15:53:36 -0800, Christophe Pettus wrote:
From my understanding, the problem only occurs over streaming
replication; if the secondary was never a hot standby, and only used
the archived WAL segments,
On May 26, 2012, at 9:17 AM, Tom Lane wrote:
Would you guys please try this in the problem databases:
select a.ctid, c.relname
from pg_attribute a join pg_class c on a.attrelid=c.oid
where c.relnamespace=11 and c.relkind in ('r','i')
order by 1 desc;
If you see any block numbers above
On May 27, 2012, at 12:53 PM, Tom Lane wrote:
Another thing that can be deduced from those stack traces is that sinval
resets were happening. For example, in the third message linked above,
the heapscan is being done to load up a relcache entry for relation 2601
(pg_am). This would be
columns of the pg_attribute rows for system catalogs, and seeing
if any have large block numbers.
Definitely wasn't done by me and I'm pretty sure the customer wouldn't have
done that either.
---
Jeff Frost j...@pgexperts.com
CTO, PostgreSQL Experts, Inc.
Phone: 1-888-PG-EXPRT x506
FAX: 415
On May 25, 2012, at 7:12 PM, Tom Lane wrote:
Jeff Frost j...@pgexperts.com writes:
In our customer's case, the size of pg_attribute was a little less than 1/4
of shared_buffers, so might not be the syncscan?
Could you go back and double check that? If the shared_buffers setting
were 7GB
for both PostgreSQL and MySQL.
One of my customers is trying it out currently.
--
Jeff Frost, Owner [EMAIL PROTECTED]
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
---(end of broadcast
On Tue, 26 Sep 2006, Tom Lane wrote:
Jeanna Geier [EMAIL PROTECTED] writes:
[ hostssl works with 'trust' but not 'md5' ]
It's only when I change the connection method to 'md5' that I'm running into
problems -- then I cannot connect from pgadmin or the command line.
As for Jeanna's problem,
On Tue, 26 Sep 2006, Jeff Frost wrote:
As for Jeanna's problem, I don't see any password prompt at all in her
example. I've forgotten the details, but wasn't there a password
prompting problem with 8.0.x on Windows?
It worked great with 8.1.4. Let me download 8.0.8 and try that on Windows
On Tue, 26 Sep 2006, Tom Lane wrote:
Jeff Frost [EMAIL PROTECTED] writes:
Do you remember if the problem was on the 8.0.8 server side that caused the
lack of prompting?
No, I'm pretty sure it was a client-side issue (and I thought we'd fixed
it by 8.0.8 anyway, so I'm glad to see your test
On Tue, 26 Sep 2006, Tom Lane wrote:
Jeff Frost [EMAIL PROTECTED] writes:
Interestingly, I receive the same error when I disable SSL on the server:
If SSL is disabled then hostssl lines in pg_hba.conf effectively become
no-ops --- they can never be matched since no incoming connection
On Tue, 26 Sep 2006, Jeff Frost wrote:
But, when I put the trust line back with hostssl, I do not get connected as
per her original indication. Of course this is with my 8.1.4 windows server
and not 8.0.8. Is it possible that 8.0.8 was more liberal with the hostssl
vs host interpretation
On Tue, 26 Sep 2006, Jeanna Geier wrote:
Any thoughts?? Like I said previously, I did build this on Windows from
source so we could use the SSL option.could I have missed something when
I was doing that? (It was my first time and I was following instructions from
the INSTALL docs)
On Tue, 26 Sep 2006, Alvaro Herrera wrote:
Jeanna Geier wrote:
Searched again for 'pgpass' and for the 'Application Data' directory with
no luck...
The file is called pgpass.conf on Windows. As for the Application
Data, it may be called differently if your Windows is localized -- try
objects at once.
Apparently, each large object is around 80MB in size, so I suspect it's not
difficult to overwhelm autovacuum if you remove quite a few of these at one
time.
--
Jeff Frost, Owner [EMAIL PROTECTED]
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908
On Sun, 21 May 2006, Jeff Frost wrote:
So the chances of the original problem being archiver related are
receding...
This is possible, but I guess I should try and reproduce the actual problem
with the same archive_command script and a CIFS mount just to see what
happens. Perhaps the real
or inspirations, I'm all ears!
--
Jeff Frost, Owner [EMAIL PROTECTED]
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
---(end of broadcast)---
TIP 6: explain analyze is your friend
if that could be it.
--
Jeff Frost, Owner [EMAIL PROTECTED]
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http
archive_command script and a CIFS mount just to see what
happens. Perhaps the real root of the problem is elsewhere, it just seems
strange since the archive_command is the only postgres related process that
accesses the CIFS share. More later.
--
Jeff Frost, Owner [EMAIL PROTECTED]
Frost
a patch since I've already got this test
case setup.
--
Jeff Frost, Owner [EMAIL PROTECTED]
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
---(end of broadcast)---
TIP 1: if posting/reading
looked through /var/log/messages* and there wasn't a restart prior to the
problem in the logs. They go back to April 16. The postmaster was restarted
on May 15th (this Monday), but that was after the reported problem.
--
Jeff Frost, Owner [EMAIL PROTECTED]
Frost Consulting, LLC http
to reproduce the problem?
--
Jeff Frost, Owner [EMAIL PROTECTED]
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ
22 matches
Mail list logo
