On 30 May 2012, at 1:16, Tim Uckun wrote:
> I am wondering if either of these features are on the plate for
> postgres anytime soon? I see conversations going back to 2007 on
> updateable views and some conversations about synonyms but obviously
> they have never been added to the database for som
On Wed, May 30, 2012 at 9:03 AM, yi huang wrote:
> It turns out i also need to define a type for the result record of `foo`,
> because record can't reveal the structure of the result (it complains:
> record "r" has no field "somerow").
> I have to created this type:
>
> create type foo_result as
On Wed, May 30, 2012 at 12:38 PM, Alban Hertroys wrote:
> On 30 May 2012, at 1:16, Tim Uckun wrote:
>
> > I am wondering if either of these features are on the plate for
> > postgres anytime soon? I see conversations going back to 2007 on
> > updateable views and some conversations about synonyms
So,
If you haven't heard the news yet, google is migrating off MySQL for
adwords. They decided to implement their own system, F1:
http://static.googleusercontent.com/external_content/untrusted_dlcp/research.google.com/en/us/pubs/archive/38125.pdf
It's a distributed SQL system, but they opted no
On 05/29/2012 07:08 PM, Adrian Klaver wrote:
On 05/29/2012 04:28 PM, David Salisbury wrote:
On 5/27/12 12:25 AM, Jasen Betts wrote:
The query: "show integer_datetimes;" should return 'on' which means
timestamps are microsecond precision if it returns 'off' your database
was built with floatin
CentOS 5.x (now 5.8), Postgres 8.4.something. Postgres had been up and
running for over a year now.
After an update on the system, and adding mod_ssl in Apache (is this
related? No idea.), Postgres no longer starts up. It just fails silently.
"pgstartup.log" contains only one single line:
Hi
Please assist, I am junior DBA. We are upgrading from postgres 7.3.4 where
we were using SQL_ASCII Encoding to Postgres 9.1.2. It looks like Postgres
9.1.2 forces you to use UTF8 Encoding if I read from this link
http://www.postgresql.org/docs/9.1/static/release-9-1-2.html . Can we still
use
On Wed, May 30, 2012 at 8:55 PM, Bart Lateur wrote:
> CentOS 5.x (now 5.8), Postgres 8.4.something. Postgres had been up and
> running for over a year now.
>
> ** **
>
> After an update on the system, and adding mod_ssl in Apache (is this
> related? No idea.), Postgres no longer starts up. It
On Wed, May 30, 2012 at 11:58 PM, Khangelani Gama wrote:
> Hi
>
>
>
> Please assist, I am junior DBA. We are upgrading from postgres 7.3.4 where
> we were using SQL_ASCII Encoding to Postgres 9.1.2. It looks like Postgres
> 9.1.2 forces you to use UTF8 Encoding if I read from this link
> http://ww
Hi
We were getting this error.
ERROR: invalid byte sequence for encoding "UTF8": 0xa0
We are thinking of using SQL_ASCII in postgres 9.1.2
And that we will be feeding from backup server(UTF-8) into another server
that’s using SQL_ASCII. Where are not if it’ll be fine to feed from UTF-
On 05/30/12 8:25 AM, Bart Lateur wrote:
After an update on the system, and adding mod_ssl in Apache (is this
related? No idea.), Postgres no longer starts up. It just fails
silently. “pgstartup.log” contains only one single line:
runuser: cannot set groups: Operation not permitted
did yo
On 05/30/12 10:17 AM, Khangelani Gama wrote:
So talking about compatibility, you are saying we can continue using
UTF-8?, but this will create more work for us because most of our
scripts assume that encoding is SQL_ASCII hence we want continue
using SQL_ASCII in Postgres 9.1.2.
SQL_ASCII is
Many Thanks for feedback.
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: Wednesday, May 30, 2012 7:54 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] What's a correct or good Encoding for
Does 9.2 support an array of ranges? For example, I have the following
int4ranges => [0,5999) and [7000, 7999) which needs to be associated with
the same record.
Thanks,
Dave
(Sorry if message threading is a bit off; I'm replying from a different
mail account as the previous post, so the "ref" header won't match.)
Well I tried
/usr/bin/pg_ctl -D /var/lib/pgsql/data start -l /tmp/pglogfile
and it just says
server starting
and then... nothing. It seem
On Wed, May 30, 2012 at 1:59 PM, Dave Bettin wrote:
> Does 9.2 support an array of ranges? For example, I have the following
> int4ranges => [0,5999) and [7000, 7999) which needs to be associated with
> the same record.
yup:
postgres=# select array['[0,5999)'::int4range];
array
Bart:
Failing a more definitive diagnostic approach, I suggest that you post
your entire pgstartup.log rather than just the error message. My guess
is that the position in that log where the error occurs will give folks
who are more familiar with the startup sequence a reasonable idea of
whe
In theory...(not running 9.2 that I could test):
{"[0,5999)","[7000,7999)"}::int4range[]
Not sure the exact type name for the int4range. The double quotes are
necessary. The curly-braces surround the whole array and elements are
separated by commas.
David J.
On May 30, 2012, at 14:59, Dave
On Wednesday, May 30, 2012 08:22:58 PM Bart Lateur wrote:
> Luckily this is a development machine, but as we don't know what causes
> the problem we fear we might one day face the exact same problem where
> it does matter: on a production machine. So we'd like to know exactly
> what went wrong..
C
Alan Hodgson writes:
> On Wednesday, May 30, 2012 08:22:58 PM Bart Lateur wrote:
>> Luckily this is a development machine, but as we don't know what causes
>> the problem we fear we might one day face the exact same problem where
>> it does matter: on a production machine. So we'd like to know exa
On 5/30/12 9:42 AM, Adrian Klaver wrote:
Think I realize where the confusion is now. When Jasen mentioned integer
datetimes he was referring to the internal storage format Postgres uses
to record the datetime value. Via the magic of programming(others will
have to fill that part in) the interna
On Tue, 2012-05-08 at 15:11 +0300, Oleg Mürk wrote:
> Hello,
>
> Our postgresql logs are getting filled with warnings:
> LOG: picksplit method for column COLUMN_IDX of index INDEX_NAME
> doesn't support secondary split
> We are using gist indexes on integer, timestamp, and Postgis geometry.
>
>
On 05/30/2012 01:48 PM, David Salisbury wrote:
On 5/30/12 9:42 AM, Adrian Klaver wrote:
Think I realize where the confusion is now. When Jasen mentioned integer
datetimes he was referring to the internal storage format Postgres uses
to record the datetime value. Via the magic of programming(ot
On Mon, 2012-04-30 at 17:23 -0400, Andrew Hannon wrote:
> 1. Is our data intact? PG eventually starts up, and it seems like once
> the streaming suffers the FATAL error, it falls back to performing log
> restores.
I don't see anything alarming there. Postgres will not start up if it
thinks it's r
On Wed, 2012-05-30 at 09:56 +0800, Craig Ringer wrote:
> On 05/29/2012 02:27 AM, Alexander Reichstadt wrote:
> > Hi,
> >
> > I am trying to "simply" export my postgres database from one server and
> > then import it into another. I thought I could use PhpPgAdmin, but the
> > hints on the web don'
Awesome, I will give it a try.
Thanks!
On Wed, May 30, 2012 at 1:00 PM, David Johnston wrote:
> In theory...(not running 9.2 that I could test):
>
> {"[0,5999)","[7000,7999)"}::int4range[]
>
> Not sure the exact type name for the int4range. The double quotes are
> necessary. The curly-braces
Hi,
On Fri, 2012-05-25 at 17:56 +0800, Craig Ringer wrote:
> Hi all
>
> I just had the ... pleasure ... of using Windows with Pg again and was
> in a usability review frame of mind. I landed up trying to restore my
> database using PgAdmin-III, and was astonished at how difficult and
> painfu
On Fri, 2012-05-25 at 19:15 +0800, Craig Ringer wrote:
> On 25/05/2012 6:55 PM, Marti Raudsepp wrote:
> > Together with an earlier study about common PostgreSQL pitfalls, I've
> > created an article on the wiki:
> > https://wiki.postgresql.org/wiki/Usability_reviews
> >
> > However, I suspect posti
I am part of a team that fills an operational roll administering 1000+ servers
and
100's of applications. Of course we need to "read" all of our logs, and must
use computers to
help us. In filtering postgreSQL logs there is one thing that makes life
difficult for us admins.
Nice things about th
Evan Rempel writes:
> Even when the wrap column is set to a very large value (32k) STATEMENT lines
> still wrap according to the line breaks in
> the original SQL statement.
> Wrapped line no longer have the prefix - difficult to grep the log for
> everything pertaining to a particular database
On Thu, May 31, 2012 at 2:05 PM, Evan Rempel wrote:
> Even when the wrap column is set to a very large value (32k) STATEMENT lines
> still wrap according to the line breaks in
> the original SQL statement.
The problem isn't so much the wrapping, it seems, as that your
statements' line breaks are
Can this be done to syslog destination?
Evan Rempel
Systems Administrator
University of Victoria
On 2012-05-30, at 10:37 PM, "Tom Lane" wrote:
> Evan Rempel writes:
>> Even when the wrap column is set to a very large value (32k) STATEMENT lines
>> still wrap according to the line breaks in
>>
32 matches
Mail list logo
