On 04/06/2017 08:01 PM, rob stone wrote:
On Thu, 2017-04-06 at 15:58 -0700, Adrian Klaver wrote:
On 04/06/2017 03:16 PM, rob stone wrote:
Which is what has me confused. If you are using the postgresql-
common
system then the *.conf files should be in
On Thu, 2017-04-06 at 15:58 -0700, Adrian Klaver wrote:
> On 04/06/2017 03:16 PM, rob stone wrote:
> >
> >
>
> Which is what has me confused. If you are using the postgresql-
> common
> system then the *.conf files should be in
> /etc/postgresql/version/cluster_name/.
>
> Where exactly is
2017-04-07 14:19 GMT+12:00 David G. Johnston :
> On Thu, Apr 6, 2017 at 7:15 PM, Patrick B
> wrote:
>
>>
>> David,
>> That won't work.
>>
>
> Actually, it works fine, you just keep moving the under-specified problem
> space.
>
> I'd
On Thu, Apr 6, 2017 at 7:15 PM, Patrick B wrote:
>
> David,
> That won't work.
>
Actually, it works fine, you just keep moving the under-specified problem
space.
I'd suggest creating a self-contained running example that gets you close
and show what the final output
On Apr 7, 2017 4:16 AM, "Patrick B" wrote:
2017-04-07 14:08 GMT+12:00 David G. Johnston :
> On Thu, Apr 6, 2017 at 6:33 PM, Patrick B
> wrote:
>
>> When actually I just want the 'main''
>>
>
> SELECT * FROM tbl
On Apr 7, 2017 4:08 AM, "David G. Johnston"
wrote:
On Thu, Apr 6, 2017 at 6:33 PM, Patrick B wrote:
> When actually I just want the 'main''
>
SELECT * FROM tbl WHERE path_name ~ '/main$' ?
David J.
Or just:
SELECT 'main';
2017-04-07 14:08 GMT+12:00 David G. Johnston :
> On Thu, Apr 6, 2017 at 6:33 PM, Patrick B
> wrote:
>
>> When actually I just want the 'main''
>>
>
> SELECT * FROM tbl WHERE path_name ~ '/main$' ?
>
> David J.
>
>
David,
That won't work.
On Thu, Apr 6, 2017 at 6:33 PM, Patrick B wrote:
> When actually I just want the 'main''
>
SELECT * FROM tbl WHERE path_name ~ '/main$' ?
David J.
2017-04-06 18:10 GMT+12:00 Patrick B :
>
> 2017-04-06 17:35 GMT+12:00 Arjen Nienhuis :
>
>>
>>
>> On Apr 6, 2017 05:57, "Patrick B" wrote:
>>
>> Hi guys,
>>
>> i've got this column:
>>
>> path_name character varying(255)
On 04/06/2017 03:16 PM, rob stone wrote:
On Wed, 2017-04-05 at 21:14 -0700, Adrian Klaver wrote:
What repos are you using, the Debian or the PGDG one?
I guess the question I should really ask is, are you using a repo or
some other method to upgrade?
Upgraded from standard Debian repos.
On Wed, 2017-04-05 at 21:14 -0700, Adrian Klaver wrote:
>
> What repos are you using, the Debian or the PGDG one?
>
> I guess the question I should really ask is, are you using a repo or
> some other method to upgrade?
>
>
Upgraded from standard Debian repos.
Nothing else was changed
On 04/04/2017 11:52 PM, Tom DalPozzo wrote:
Hi,
2017-04-05 1:55 GMT+02:00 Adrian Klaver >:
On 04/04/2017 07:45 AM, Tom DalPozzo wrote:
Postgres version?
9.6.1
Hi,
I had two replication slots on my primary.
On Thu, Apr 6, 2017 at 8:51 AM, Tom DalPozzo wrote:
>
> What is the meaning of FPI_FOR_HINT?
>
>
Full Page Image for Hint [Bits]
Its noted as being dependent upon checksums being enabled.
I have a feel for the interactions involved here but not enough to explain
them
2017-04-04 19:18 GMT+02:00 Scott Marlowe :
> On Tue, Apr 4, 2017 at 9:46 AM, Tom DalPozzo wrote:
> > Hi,
> > I have a very big table (10GB).
> > I noticed that many WAL segments are being written when elaborating read
> > only transactions like
On Thu, Apr 6, 2017 at 4:24 AM, Moreno Andreo
wrote:
> psql -h localhost postgres -c "copy (SELECT * FROM a WHERE time < now()) to
> stdout " | psql -h localhost postgres -c "copy b from stdin"
The first question at hand is whether the source psql command will
On Thu, Apr 6, 2017 at 3:46 PM, Stephen Frost wrote:
> Tom,
>
> * Tom Lane (t...@sss.pgh.pa.us) wrote:
> > (But ... these statements are based on an assumption of out-of-the-
> > box Postgres behavior. I would not exactly put it past the Debian
> > packagers to have decided
On Thu, Apr 6, 2017 at 4:27 AM, Ertan Küçükoğlu
wrote:
> Sorry for top posting.
>
> I have a serial in master table because I need to know data insertion order.
> DateTime on Raspberry Pi is not accurate due to power loss and lack of
> internet access to fetch correct
Il 06/04/2017 16:10, pinker ha scritto:
Error message says, as one could expect, that the second table has got smaller
precision...
The question isn't about this particular error - which was induced for purpose
- but about atomicity of this operation
Sorry, I read your message without paying
On 04/06/2017 06:40 AM, Ertan Küçükoğlu wrote:
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Thursday, April 6, 2017 4:18 PM
To: Ertan Küçükoğlu ;
pgsql-general@postgresql.org
Subject: Re: [GENERAL] Advise on primary key for
W dniu 2017-04-06 14:28:04 użytkownik Moreno Andreo
napisał:
> Il 06/04/2017 13:58, pinker ha scritto:
> >
> > W dniu 2017-04-06 13:24:16 użytkownik Moreno Andreo
> > napisał:
> >> Il 05/04/2017 23:26, pinker ha scritto:
> >>> Hi,
> >>> I'm
Tom,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> (But ... these statements are based on an assumption of out-of-the-
> box Postgres behavior. I would not exactly put it past the Debian
> packagers to have decided to change this for reasons of their own,
> and their track record of telling us about
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Thursday, April 6, 2017 4:18 PM
To: Ertan Küçükoğlu ;
pgsql-general@postgresql.org
Subject: Re: [GENERAL] Advise on primary key for detail tables (OS:
Raspberry Pi)
> On
On 04/06/2017 03:27 AM, Ertan Küçükoğlu wrote:
Sorry for top posting.
I have a serial in master table because I need to know data insertion order.
DateTime on Raspberry Pi is not accurate due to power loss and lack of
internet access to fetch correct time from.
Understand, though it does beg
Il 06/04/2017 13:58, pinker ha scritto:
W dniu 2017-04-06 13:24:16 użytkownik Moreno Andreo
napisał:
Il 05/04/2017 23:26, pinker ha scritto:
Hi,
I'm trying to write an archive manager which will be first copying data from
tables with where clause and then, after
On Thu, Apr 06, 2017 at 12:05:51AM -0400, Tom Lane wrote:
> rob stone writes:
> > Upgraded to version 9.6.2-2 and these are the log entries on start-up:-
>
> > 2017-04-05 08:03:29 AESTLOG: test message did not get through on
> > socket for statistics collector
...
>
W dniu 2017-04-06 13:24:16 użytkownik Moreno Andreo
napisał:
> Il 05/04/2017 23:26, pinker ha scritto:
> > Hi,
> > I'm trying to write an archive manager which will be first copying data from
> > tables with where clause and then, after successful load into second
Il 05/04/2017 23:26, pinker ha scritto:
Hi,
I'm trying to write an archive manager which will be first copying data from
tables with where clause and then, after successful load into second server
- delete them.
The simplest (and probably fastest) solution I came up with is to use copy:
psql -h
Sorry for top posting.
I have a serial in master table because I need to know data insertion order.
DateTime on Raspberry Pi is not accurate due to power loss and lack of
internet access to fetch correct time from.
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
2017-04-06 17:35 GMT+12:00 Arjen Nienhuis :
>
>
> On Apr 6, 2017 05:57, "Patrick B" wrote:
>
> Hi guys,
>
> i've got this column:
>
> path_name character varying(255)
>>
>
> I store full S3 bucket path for the attachments of my application on it;
29 matches
Mail list logo