On Thu, Oct 10, 2013 at 1:24 AM, wrote:
> my postgresql running file . but sometime i found cache lookup failed for
> relation 421062806 error in postgresql log. can anyone tell me significant
> of this error.
A relation has disappeared even if the session hold a sufficient lock
on it, ensuring t
On Sat, Oct 5, 2013 at 9:38 PM, Dave Page wrote:
>
>
>> On 5 Oct 2013, at 13:21, Michael Paquier wrote:
>>
>>> On Fri, Oct 4, 2013 at 11:36 AM, Paragon Corporation wrote:
>>> Disregard my bug complaint. Stupid user error.
>> Btw, the next time you fin
On Fri, Oct 4, 2013 at 11:36 AM, Paragon Corporation wrote:
> Disregard my bug complaint. Stupid user error.
Btw, the next time you find an error with this installer, you should
not use this mailing list for this purpose but contact directly EDB as
this installer is maintained by them and not by
On Thu, Sep 12, 2013 at 10:21 AM, wrote:
> Bug reference: 8449
> I'm not able to link in Access to the table "map". I get an ODBC error and
> in the table fields are no data, it returns "#Name?".
>
> Any idea what is wrong ?
You should be more precise here:
- What is the version of ODBC driv
On Sat, Sep 14, 2013 at 4:15 PM, wrote:
> in short, for pgadmin...
This feature request is related to PGAdmin and not Postgres core. You
should send such requests to the PGAdmin mailing lists which are
listed here:
http://www.pgadmin.org/support/list.php
Regards,
--
Michael
--
Sent via pgsql
On Tue, Sep 17, 2013 at 4:48 PM, Marcelo Bacha wrote:
> I have an OpenBSD 5.3 server, with PostgreSQL 9.3.0, which seems to work
> fine. I´m trying to install on it, which always worked fine.
Postgres is working fine as you mention, and only PostGIS development
failed. Based on the information ab
On Tue, Sep 17, 2013 at 1:52 AM, Saravanan Nagarajan
wrote:
> In pglog_txt,
>
> LOG: could not bind IPv6 socket: No error
> HINT: Is another postmaster already running on port 33307? If not, wait a
> few seconds and retry.
> LOG: could not bind IPv4 socket: No error
> HINT: Is another postmast
On Mon, Sep 9, 2013 at 12:55 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8440
> Logged by: Jitendra Sabat
> Email address: sabat.jitendr...@gmail.com
> PostgreSQL version: Unsupported/Unknown
> Operating system: Window server 2012
> Descr
On Mon, Sep 9, 2013 at 11:38 PM, Sbis-Partner wrote:
> Hello!
>
> When you restore a database error occurs
>
> «Pg_restore: creating TABLE dbschema
>
> pg_restore: [archiver (db)] Error from TOC entry 1428; 1259 83487 TABLE
> dbschema User
>
> pg_restore: [archiver (db)] could not execute query: E
On Wed, Sep 11, 2013 at 4:00 AM, Saravanan Nagarajan
wrote:
> Hi,
>
> I am using PostgreSQL. If am starting the db with System Account/ any domain
> account using wrapper, the DB is starting fine.
>
> If i am trying to start the PostgreSQL DB using command prompt, [Normal mode
> or Run as administ
On Fri, Aug 30, 2013 at 2:13 PM, wrote:
> However, I think error message should filter dropped column and strange null
> values (because if a table has a lot dropped column this error message
> quickly become completely unreadable).
Yes, this is not really user-friendly. This comes from
ExecBuild
On Wed, Aug 14, 2013 at 11:00 PM, David Fetter wrote:
> On Sun, Aug 11, 2013 at 08:06:55AM +, rohit.gupta...@gmail.com wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 8381
>> Logged by: Rohit Gupta
>> Email address: rohit.gupta...@gmail.com
>
It looks that you are missing something. Similarly to what you did, here is
an example of PITR using a base backup:
1) Here is my master node doing some archiving:
$ psql -c 'show archive_command' -p 5432
archive_command
On Mon, Aug 12, 2013 at 1:53 AM, ascot.m...@gmail.com
wrote:
> I want to enable WAL archive on the replica, I am advised that WAL archive
> can only be enabled on the Master, can you please advise if this is a bug
> and any workaround available?
Archiving a WAL file is only done once its generatio
On Wed, Jul 31, 2013 at 6:58 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8346
> Logged by: Devadas Mallya
> Email address: devadas_mal...@yahoo.co.in
> PostgreSQL version: 9.2.0
> Operating system: Ubuntu 12.04 Server Edition (64-bit)
> D
On Wed, Jul 31, 2013 at 2:12 AM, Pavel Stehule wrote:
> Hello
>
> 2013/7/30 :
> > The following bug has been logged on the website:
> >
> > Bug reference: 8345
> > Logged by: Arun Kumar
> > Email address: arun...@gmail.com
> > PostgreSQL version: Unsupported/Unknown
> > Operati
On Fri, Jul 26, 2013 at 7:28 PM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8336
> Logged by: Harsh Vardhan Upadhyay
> Email address: harshmailbo...@gmail.com
> PostgreSQL version: 9.2.2
> Operating system: windows
> Description:
>
> Dear Si
On Tue, Jul 23, 2013 at 2:24 PM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8325
> Logged by: Robert Stone
> Email address: floripa...@gmail.com
> PostgreSQL version: 9.2.4
> Operating system: Linux roblaptop 3.9-1-amd64 #1 SMP Debian 3.9.8-
On Tue, Jul 23, 2013 at 2:02 PM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8324
> Logged by: Robert Stone
> Email address: floripa...@gmail.com
> PostgreSQL version: 9.2.4
> Operating system: Debian 3.9-1-amd64 #1 SMP Debian 3.9.8-1 x86_64
On Fri, Jul 5, 2013 at 8:11 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8286
> Logged by: Eike Dierks
> Email address: e...@inter.net
> PostgreSQL version: 9.2.4
> Operating system: CentOS release 6.4
> Description:
>
> I believe to have
On Wed, Jun 26, 2013 at 9:21 PM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8255
> Logged by: gabriel
> Email address: gabriel...@santamonicace.com.br
> PostgreSQL version: 8.4.4
You are missing many minor releases. The latest version of 8.4 i
On Sat, Jun 1, 2013 at 3:34 AM, wrote:
> initdb: removing contents of data directory "C:/Program Files
> (x86)/PostgreSQL/8.1/data"
>
Only Postgres 8.1 is not supported anymore by the community for a couple of
years.
You should use a newer version.
--
Michael
On Fri, May 31, 2013 at 1:51 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8193
> Logged by: Lajos Veres
> Email address: vla...@gmail.com
> PostgreSQL version: 9.2.4
> Operating system: Linux
> Description:
>
> Found a few small misspell w
Hi,
This is not really a PostgreSQL bug, so you should contact directly Slony
people using a mailing list like this one:
http://lists.slony.info/mailman/listinfo/slony1-general
Thanks,
--
Michael
On Fri, Mar 22, 2013 at 5:12 AM, wrote:
> run a batch in pgAgent the following error occurs.
>
> DEBUG: Checking for jobs to run
> DEBUG: Sleeping... sh: /tmp/pga_GvQxqM/5_9.scr: Permission denied
> DEBUG: Clearing inactive connections
> DEBUG: Connection stats: total - 1, free - 0, deleted - 0
On Tue, Feb 19, 2013 at 5:50 PM, Peter Kroon wrote:
> Also no result with FROM __my_table LIMIT 1;
>
I'm having correct results with PG 9.2 by using either xmlagg or xmlelement.
For example:
postgres=# SELECT xmlelement(name el_name, id) FROM __table LIMIT 1;
xmlelement
Hi,
With your query and such tables:
create table __table (id int);
insert into __table values (1),(2);
create table __table_to_table (id int, table_id int);
insert into __table_to_table values (1, 1),(2, 2);
I am getting consistent results with 9.2.1 and 9.2.3 on my Linux box, hence:
27 matches
Mail list logo
