If I understand correctly, you're looking for Postgres hosted as a service?
Heroku provides hosting as a service [1], and we do allow you to connect
from anywhere. It's true that generally folks in the Postgres community
prefer to run databases with perimeter security and only leave your
database d
On Mon, Jan 26, 2015 at 2:38 PM, Tim Smith
wrote:
> create table templates(
>template_id int not null primary key,
>template_groupid int not null,
>template_version int not null
>template_text text not null);
>
> Would I need to resort to using a CTE or subquery to make this sort
On Fri, Jan 23, 2015 at 12:08 PM, Al Eridani wrote:
> Is this still true on the 9.x versions? Thanks!
>
It is, unfortunately. If your client kicks off a 12h query and immediately
closes the TCP connection, Postgres won't notice until the query has
completed.
Thanks, everyone. That seems to be it. I still haven't gotten it to work (I
tried setting OPENSSL_DEFAULT_ZLIB=true in
/etc/postgresql/9.2/main/environment and restarting the server, then adding
the same env var when connecting with the client), but now that I know
where the problem is, I think I c
I'm having a hard time getting SSL compression working (or even figuring
out why it's not working) with my local Postgres server. The setting [1] is
documented to default to on, but according to the banner when I connect
with psql, it's off. It's still off even if I explicitly set
PGSSLCOMPRESSION=
On Mon, May 26, 2014 at 12:24 AM, Andres Freund wrote:
> Any chance you're using a 9.3 configuration file instead of the one
> generated by initdb?
> dynamic_shared_memory_type defaults to 'posix' if not specified in the
> config file (on platforms supporting it). If initdb detects that 'posix'
>
On Tue, May 27, 2014 at 8:23 PM, Robert Haas wrote:
>
> I think it would be good to understand why initdb isn't getting this
> right. Did you run initdb outside the LXC container, where /dev/shm
> would have worked, but then run postgres inside the LXC container,
> where /dev/shm does not work?
ere, but 9.0 through 9.3 run just fine in the same configuration. Any idea
what may have changed? I suspect the solution here is tweaking some LXC
setting, but I was hoping someone can point me in the right direction.
Thanks,
Maciek Sakrejda
Heroku Postgres
On Tue, Mar 5, 2013 at 10:23 AM, Tom Lane wrote:
>> Why the discrepancy between
>> default behavior and what pg_dump gets?
>
> Basically, the default behavior is tuned to the expectations of people
> who think that what they put in is what they should get back, ie we
> don't want the system doing
On Tue, Mar 5, 2013 at 12:03 AM, Albe Laurenz wrote:
> I don't think that it is about looking nice.
> C doesn't promise you more than FLT_DIG or DBL_DIG digits of
> precision, so PostgreSQL cannot either.
>
> If you allow more, that would mean that if you store the same
> number on different platf
On Sun, Mar 3, 2013 at 9:14 PM, Tom Lane wrote:
> The real difficulty is that there may be more than one storable value
> that corresponds to "1.23456" to six decimal digits. To be certain that
> we can reproduce the stored value uniquely, we have to err in the other
> direction, and print *more*
While having more docs around extra_float_digits is a great idea, I
don't think the patch really clarifies much.
(Disclaimer: I honestly have only a vague idea of the reasoning behind
extra_float_digits existing in the first place, but perhaps that means
I'm a good target audience for the doc patc
omething else I'm missing?
Thanks,
[1]: http://www.postgresql.org/docs/8.3/static/sql-copy.html
---
Maciek Sakrejda | System Architect | Truviso
1065 E. Hillsdale Blvd., Suite 215
Foster City, CA 94404
www.truviso.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
or hstore quote exactly like arrays, so that's probably
> part of your problem. (No doubt it'd be better if they did, but we've
> got too much historical baggage :-()
I understand completely.
Thanks for your help,
---
Maciek Sakrejda | System Architect | Truviso
1065 E. Hillsdale
trying to reverse engineer the behavior by using the
ARRAY[...] syntax, but I can't figure out the logic. Any suggestions
(other than to run screaming from this affront to proper relational
design--I have my reasons for it)?
Thanks,
---
Maciek Sakrejda | System Architect | Truviso
1065 E. Hill
Hi,
Is there any way to get log_min_duration_statement / log_statement /
log_duration to work with queries issued through SPI? If this is not
possible with a stock configuration, anyone of a patch that might be
floating out there to add this?
Thanks,
---
Maciek Sakrejda | System Architect
16 matches
Mail list logo
