On 16/12/12 18:23, Terence Ferraro wrote:
On Sat, Dec 15, 2012 at 11:54 PM, Gavin Flower
mailto:gavinflo...@archidevsys.co.nz>>
wrote:
Please do not top post, see end of email for rest of reply...
(Bottom posting is the convention here, so people can see the
context before readin
On Sat, Dec 15, 2012 at 11:54 PM, Gavin Flower <
gavinflo...@archidevsys.co.nz> wrote:
> Please do not top post, see end of email for rest of reply...
> (Bottom posting is the convention here, so people can see the context
> before reading your reply.)
>
>
>
> On 16/12/12 16:52, Terence Ferraro w
Please do not top post, see end of email for rest of reply...
(Bottom posting is the convention here, so people can see the context
before reading your reply.)
On 16/12/12 16:52, Terence Ferraro wrote:
Sorry about the double post, I thought the list disallowed attachments
so I sent it again w
Sorry about the double post, I thought the list disallowed attachments so I
sent it again with a pastebin link instead of an attachment.
This change does not affect the storage at all. If it did, pre-9.1 things
would have been a mess. Rather, this allows the system to determine the
timezone for lo
On 16/12/12 16:07, Terence Ferraro wrote:
We recently began upgrading our clients' servers from 9.0 -> 9.2.
After a few deployments and a little digging we noticed that 9.0 ->
9.1 broke the use of no timezone set within postgresql.conf. That is,
not setting the option was now defaulting to GMT
We recently began upgrading our clients' servers from 9.0 -> 9.2. After a
few deployments and a little digging we noticed that 9.0 -> 9.1 broke the
use of no timezone set within postgresql.conf. That is, not setting the
option was now defaulting to GMT instead of the system timezone.
Unfortunately,
The primary key only ensures uniqueness on the specific table that you are
working with, not across an entire inheritance chain. Likewise, Foreign
Keys are linked to explicit tables and not the inheritance chain as a whole.
In your example "p_table" does NOT have value of "2", "c_table" is whe
Dear all,
I'm new to PostgreSQL. I currently have a problem with the foreign key
constraint to a parent table in PostgreSQL.
I have three tables p_table, c_table, and r_table as the following.
-
CREATE TABLE p_table
(
id seria
On Sat, Dec 15, 2012 at 10:16:55PM +0100, Peter Bex wrote:
> A simple sed(1) expression should do the trick:
>
> sed -E 's/ +/ /g' old-file > new-file
I just remembered where I could check, and the GNU sed equivalent is:
sed -r 's/ +/ /g' old-file > new-file
Sorry for the confusion.
Cheers,
Pe
On Sat, Dec 15, 2012 at 08:06:44PM +0100, Andreas wrote:
> Hi,
>
> Problem here is in the morning the first digit of the hour is shown as a
> blank so there are 2 blanks before the time so COPY misstakes this as an
> empty column and gets confused.
>
> Can someone point me in the direction of a
On 12/15/2012 11:06 AM, Andreas wrote:
Hi,
I need to import textfiles that have 5 columns but there is just blanks
as delimitors.
I could use COPY to read them but there is a time column that shows
times as " h:mm.ss,ms" in the morning and "hh:mm.ss,ms" in the afternoon.
Problem here is in the
Hi,
I need to import textfiles that have 5 columns but there is just blanks
as delimitors.
I could use COPY to read them but there is a time column that shows
times as " h:mm.ss,ms" in the morning and "hh:mm.ss,ms" in the afternoon.
Problem here is in the morning the first digit of the hour i
I wrote:
> Hah, I wondered if it might be something like that. Still, it's hard to
> see how this link() would fail any security check that didn't amount to
> disabling link() altogether. The UID and GID of the process, the old
> file, and the directory will all match --- so exactly what rule are
David Noel writes:
> Ugh. It turns out I had security.bsd.hardlink_check_gid=1 and
> security.bsd.hardlink_check_uid=1 in sysctl.conf. Setting them to 0
> fixed everything. That's frustrating. Sorry for all the trouble. Many
> thanks for helping resolve this.
Hah, I wondered if it might be someth
Ugh. It turns out I had security.bsd.hardlink_check_gid=1 and
security.bsd.hardlink_check_uid=1 in sysctl.conf. Setting them to 0
fixed everything. That's frustrating. Sorry for all the trouble. Many
thanks for helping resolve this.
On 12/15/12, Amitabh Kant wrote:
> David
>
> I just tried instal
I might be missing something, but what exactly does that commit give us?
I mean - we were able, previously, to make slave switch to new master
- as Phil Sorber described in here:
http://philsorber.blogspot.com/2012/03/what-to-do-when-your-timeline-isnt.html
After some talk on IRC, I understood th
David
I just tried installing PG 9.2.2 on FreeBSD 8.3 and initdb went smoothly
without any problems. the only difference would be that I had it running in
a virtualbox instance. My config were as follows;
FreeBSD 8.3-RELEASE-p5 (binary updated through freebsd-update)
PG 9.2.2 (installed through p
17 matches
Mail list logo
