What Would Happen if I got NO "localhost" entry in my /etc/hosts ?
statistics and autovacuum would be disabled:
# /usr/local/pgsql/bin/postgres -i -p 15432 -D data
LOG: could not resolve "localhost": no address associated with name
LOG: disabling statistics collector for lack of working socket
W
Hi Robert,
On Thursday, October 27, 2011 12:38:02 PM Robert Young wrote:
> What Would Happen if I got NO "localhost" entry in my /etc/hosts ?
Why should pg cater for such a broken configuration? Sorry for being harsh but
that seems like it would end in heaps of workarounds.
Andres
--
Sent via
But,I think insistence of hard-coding should be even worse than broken
configuration.
And hard-coding should never be a good work ethics of a professional programmer.
On Thu, Oct 27, 2011 at 12:12, Andres Freund wrote:
> Hi Robert,
>
> On Thursday, October 27, 2011 12:38:02 PM Robert Young wrote:
On 27.10.2011 15:57, Robert Young wrote:
But,I think insistence of hard-coding should be even worse than broken
configuration.
And hard-coding should never be a good work ethics of a professional programmer.
You're exaggerating. There's nothing wrong hard-coding things like
number of seconds i
In reality,sometimes something would be wrong if you hard-coding 1
minute as 60 seconds.
Please read:
http://www.openbsd.org/cgi-bin/man.cgi?query=strftime
"The range of seconds is (00-60) instead of (00-59) to allow for the
periodic occurrence of leap seconds."
so,it's a bad habit including hard-
Heikki Linnakangas writes:
> BTW, do we have anything in place to stop any user on the same host to
> send bogus stat messages to the stats collector?
Yes. Use of the connect() call is supposed to guarantee that we will
only receive packets originating from our own socket address.
As far as th
The following bug has been logged online:
Bug reference: 6273
Logged by: Justin
Email address: just...@steinhafels.com
PostgreSQL version: 9.1.1
Operating system: Windows Server 2003
Description:Install Error
Details:
On installation, it throws on error stating data
The following bug has been logged online:
Bug reference: 6274
Logged by: Jan-Peter Seifert
Email address: jan-peter.seif...@gmx.de
PostgreSQL version: 9.1
Operating system: any
Description:documentation on pg_attribute.atttypmod
Details:
Hello,
it looks like that t
On Tue, Oct 25, 2011 at 8:39 AM, Magnus Hagander wrote:
> On Mon, Oct 24, 2011 at 16:37, Keith Fiske wrote:
>> On Sat, Oct 22, 2011 at 11:49 AM, Tom Lane wrote:
>>> "Keith Fiske" writes:
>>
If you create a user as a NONsuperuser,
then later ALTER them to be one, they will NOT have the
Robert Haas writes:
> ... If we do decide to change the
> behavior, we'd better carefully document that if you want to make
> someone a superuser without giving them replication privileges (or
> revoke their superuser status without revoking replication
> privileges), you need to specify both ALT
On 28/10/11 02:13, Heikki Linnakangas wrote:
On 27.10.2011 15:57, Robert Young wrote:
But,I think insistence of hard-coding should be even worse than broken
configuration.
And hard-coding should never be a good work ethics of a professional
programmer.
You're exaggerating. There's nothing wro
Gavin Flower writes:
> Actually, a minute is not always 60 seconds, as you can legally have 62
> seconds in a minute!
There never have been, and will never be, two leap seconds declared in
the same minute --- the need for such would require that the authorities
in charge of declaring leap seco
On Thu, Oct 27, 2011 at 01:45:34PM -0400, Robert Haas wrote:
> On Tue, Oct 25, 2011 at 8:39 AM, Magnus Hagander wrote:
> > On Mon, Oct 24, 2011 at 16:37, Keith Fiske wrote:
> >> On Sat, Oct 22, 2011 at 11:49 AM, Tom Lane wrote:
> >>> "Keith Fiske" writes:
> >>
> If you create a user as a N
Noah Misch writes:
> Let's look at the behavior of DDL-exposed access constraints for precedent.
> We
> currently have three paradigms for applying access control to superusers:
> 1. Settings that affect superusers and regular users identically. These
> include
> ALTER ROLE ... LOGIN | VALID
On 27/10/2011 9:46 PM, Justin wrote:
The following bug has been logged online:
Bug reference: 6273
Logged by: Justin
Email address: just...@steinhafels.com
PostgreSQL version: 9.1.1
Operating system: Windows Server 2003
Description:Install Error
Details:
On installa
A few updates from my side:
Kevin helped me find two bugs in my test suite. The first: the test suite
had a syntax error in setting the isolation level, which resulted in not
setting an isolation level at all. Secondly, I made a mistake in the phantom
detection code, which resulted in detecting pha
The following bug has been logged online:
Bug reference: 6275
Logged by: Finlay Thompson
Email address: fin...@dragonfly.co.nz
PostgreSQL version: 8.4.9
Operating system: Ubuntu 11.04
Description:Horrible performance regression
Details:
After an upgrade from 8.4.8 t
"Finlay Thompson" writes:
> After an upgrade from 8.4.8 to 8.4.9 performance of load script went from ~
> 3 hours to not finishing after 24 hours.
> Context: We have a continuous build script, that loads, grooms, matches data
> every few hours. The script has been run over 100 times in the last f
18 matches
Mail list logo
