On 09/23/12 11:24 PM, pavithra wrote:
I have pgAdmin-III. It has version 1.12.3. I would like to run a job.
I have schedule an SQL Job. But when i run there is no output. Can
anybody let me know what needs to be done?. Also, Can any one tell,
where i need to look for the errors, when i run a jo
I have pgAdmin-III.It has version 1.12.3.I would like to run a job. I have
schedule an SQL Job. But when i run there is no output.Can anybody let me
know what needs to be done?.Also, Can any one tell, where i need to look for
the errors, when i run a job?.
--
View this message in context:
http:
Hi Rafal,
Il 24/09/12 07:54, Rafal Pietrak ha scritto:
I did what I could - the review is on the hackers list.
Thanks! That's much appreciated.
Should I do anything else to finilize this review, like "linking" it
to the pending patch? somehow? -R
You should update the commitfest.postgresq
On Tue, 2012-09-18 at 09:37 +0200, Albe Laurenz wrote:
> Rafal Pietrak wrote:
> > On Mon, 2012-09-17 at 14:31 -0500, Merlin Moncure wrote:
> > > On Mon, Sep 17, 2012 at 7:24 AM, Rafal Pietrak
> > > wrote:
[]
> >
> > Who can review that patch?
>
> You :^)
>
I did what I could - the r
=?UTF-8?Q?Gra=C5=BEvydas_Valeika?= writes:
> I just migrated to 9.2 and observing stange thing.
> While restoring 9.2 database to another server's empty database I'm getting
> several errors while restoring views:
> pg_restore: creating RULE _RETURN
> pg_restore: [archiver (db)] Error while PROC
Say I want output similar to this:
{
"id":73,
"name":"LolShirt 1",
"uuid":"afe3526818",
"thumbnails":[
{
"filename":"file.png",
"width":200,
"height":199,
"id":79
},
{
"filename":"file.png",
"width":200,
"h
Hi thanks,
I ran ps and found there were TWO postgresql
postgres 1124 0.0 0.1 45116 5480 ?SSep23 0:01
/usr/lib/postgresql/8.4/bin/postgres -D /var/lib/postgresql/8.4/main -c
config_file=/etc/postgresql/8.4/main/postgresql.conf
postgres 1133 0.0 0.0 45116 1984 ?S
On Mon, Sep 24, 2012 at 12:44 AM, Paul Ramsey wrote:
> Try just loading the 1.5 dump directly into the 2.0 database without
> the filtering step. It will be immensely noisy with lots of errors and
> warnings, but with luck you should find your data is there waiting for
> you when it's done.
>
>
I
Hi all,
I just migrated to 9.2 and observing stange thing.
While restoring 9.2 database to another server's empty database I'm getting
several errors while restoring views:
pg_restore: creating RULE _RETURN
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error
On 23/09/2012 19:31, Martin Collins wrote:
> On 23/09/12 11:48, Adrian Klaver wrote:
>> On 09/23/2012 04:47 AM, a...@hsk.hk wrote:
>>> Hi,
>>>
>>> I have upgraded postgresql 8.4.13 to 9.2.0.1 O/S Ubuntu, restarted
>>> postgresql, it displayed my postgresql is 9.2 but when I log into
>>> postgresq
On 23/09/12 11:48, Adrian Klaver wrote:
On 09/23/2012 04:47 AM, a...@hsk.hk wrote:
Hi,
I have upgraded postgresql 8.4.13 to 9.2.0.1 O/S Ubuntu, restarted
postgresql, it displayed my postgresql is 9.2 but when I log into
postgresql, show version, it is still 8.4.13, see a) and b)
below,
My
On 09/23/2012 04:47 AM, a...@hsk.hk wrote:
Hi,
I have upgraded postgresql 8.4.13 to 9.2.0.1 O/S Ubuntu, restarted postgresql,
it displayed my postgresql is 9.2 but when I log into postgresql, show version,
it is still 8.4.13, see a) and b) below,
a)
* Restarting PostgreSQL 9.2 database server
On 2012-09-23 14:47, a...@hsk.hk wrote:
Hi,
I have upgraded postgresql 8.4.13 to 9.2.0.1 O/S Ubuntu, restarted
postgresql, it displayed my postgresql is 9.2 but when I log into
postgresql, show version, it is still 8.4.13, see a) and b) below,
a)
* Restarting PostgreSQL 9.2 database server
.
Hi,
I have upgraded postgresql 8.4.13 to 9.2.0.1 O/S Ubuntu, restarted postgresql,
it displayed my postgresql is 9.2 but when I log into postgresql, show version,
it is still 8.4.13, see a) and b) below,
a)
* Restarting PostgreSQL 9.2 database server
...done.
b)
psql (8.4.13)
Type "help"
On Sat, 2012-09-22 at 20:00 -0700, Chris Travers wrote:
> On Sat, Sep 22, 2012 at 12:23 AM, Jasen Betts
> wrote:
> On 2012-09-18, Rafal Pietrak wrote:
[-]
> > could be written by user as (3):
> > SELECT 1/x AS inverse FROM data WHERE x <> 0 AND
>
On 2012-09-21, Craig Ringer wrote:
> I strongly disagree. The BOM provides a useful and standard way to
> differentiate UTF-8 encoded text files
what is stopping non utf8 files from starting with something that
looks like a BOM?
--
⚂⚃ 100% natural
--
Sent via pgsql-general mailing list
16 matches
Mail list logo