On 12/9/2017 5:46 PM, Stefan Keller wrote:
Below I re-modeled it to a relational schema as you suggested and also
tried to utilize the INHERITS feature.
Does that look better?
I believe I would use boolean, not bit.
--
john r pierce, recycling bits in santa cruz
Hi
Thanks James and Steven!
I hoped somebody will advise me not to do this.
I was just bothered with NoSQL databases.
Even TimescaleDB made me wonder because it says it scales Postgres [1]
for IoT which implies that Postsgres does not scale...
2017-12-09 23:01 GMT+01:00 Steven Lembark :
> In gene
On 12/9/2017 1:03 PM, Scott Mead wrote:
I’m guessing that the old machine was 32 but and the New is 64? They have to
match. You could always setup a 32 bit VM. It must be 32 bit windows (if that’s
what the original was )
you should be able to run 32 bit postgresql on 64 bit windows.
its a b
On Sat, 9 Dec 2017 20:22:02 +0100
Stefan Keller wrote:
> create table m1 (
> id bigint,
> created timestamp,
> b20 bit(20) default b'',
> farr20 float8[20]
> );
In general this is a bad idea *unless* you have benchmarked the
database and found that the am
On 12/9/17 12:15, Boshomi DeWiki wrote:
> Python 2.7 will not be maintained past 2020.[1]
>
> Python2 is still default for Postgres 10. CREATE EXTENSION PLPYTHONU
> results in installation of PLPYTHON2U.
>
> As of now SUSE does not support PLPYTHON3U. (This will change soon)
>
> Are there any p
> On Dec 9, 2017, at 11:11, Dale Seaburg wrote:
>
> I have a database in Windows XP (old PC), postgresql 8.4.5 which needs to be
> migrated to Windows 10 Pro (new PC).
>
> Now, for the bad news, the XP PC, when I powered down, before doing any
> backup or database unload, would not power bac
My initial inclination is to always build the simplest to understand system
first. Space is cheap and pg is pretty efficient, engineering time is expensive
and debugging time doubly so with a side of anxiety when production goes down.
Also, it will allow more flexibility later on to describe you
Hi,
Given this kind of sensors (Internet-of-Things) log and monitoring scenario:
* There are 3 production machines monitored every few seconds for
forthcoming (~2) years.
* Machine m1 is emitting 20 boolean and 20 float4 captured in sensors
(m1s1..m1s40).
* Machine m2 has same attributes as m1 pl
On 12/09/2017 09:15 AM, Boshomi DeWiki wrote:
Python 2.7 will not be maintained past 2020.[1]
Python2 is still default for Postgres 10. CREATE EXTENSION PLPYTHONU
results in installation of PLPYTHON2U.
As of now SUSE does not support PLPYTHON3U. (This will change soon)
Are there any plans fo
Python 2.7 will not be maintained past 2020.[1]
Python2 is still default for Postgres 10. CREATE EXTENSION PLPYTHONU
results in installation of PLPYTHON2U.
As of now SUSE does not support PLPYTHON3U. (This will change soon)
Are there any plans for declaring Python3 as default for Postgres 11 or
I suppose it's something I'm doing. I'm pg_dump'ing the schema with the
data, so I can't be missing any columns. However, I wrote a program to
filter out certain data. I believe that is where the problem is. I wrote
it a long, long time ago before --exclude-table-data existed. When I
use --exc
Rob Sargent writes:
>> On Dec 9, 2017, at 8:42 AM, Blake McBride wrote:
>> I am using pg_dump on version 9.5.10 and trying to import it on version
>> 9.3.20. Many (or all) COPY commands are failing with messages like:
>> psql:16504.db:16874: ERROR: missing data for column "street"
>> CONTEXT
I have a database in Windows XP (old PC), postgresql 8.4.5 which needs
to be migrated to Windows 10 Pro (new PC).
Now, for the bad news, the XP PC, when I powered down, before doing any
backup or database unload, would not power back up. I will be
attempting to get the PC fixed for that. In
> On Dec 9, 2017, at 8:42 AM, Blake McBride wrote:
>
> Greetings,
>
> I am using pg_dump on version 9.5.10 and trying to import it on version
> 9.3.20. Many (or all) COPY commands are failing with messages like:
>
> psql:16504.db:16874: ERROR: missing data for column "street"
> CONTEXT:
Greetings,
I am using pg_dump on version 9.5.10 and trying to import it on version
9.3.20. Many (or all) COPY commands are failing with messages like:
psql:16504.db:16874: ERROR: missing data for column "street"
CONTEXT: COPY address, line 1: ""
Is there an easy way for me to fix this (like e
15 matches
Mail list logo
