On Saturday, November 4, 2017, Robert Lakes wrote:
>
> Here's the error I am receiving - when I am attempting to insert a record
> into a table:
>
> ERROR: invalid input syntax for integer: "INSERT"
> LINE 1: ...T INTO listings_cdc SELECT statement_timestamp(), 'INSERT', ...
>
>
The second colum
Guys,
New to Postgres - here's my code inside an event trigger:
ELSIF (TG_OP = 'INSERT') THEN
EXECUTE format('INSERT INTO %I SELECT statement_timestamp(),
''INSERT'', $1.*', TG_TABLE_NAME || '_cdc')
USING NEW;
RETURN NEW;
Here's the error I am receiving - when I am attempt
>On 9 Oct 2017 13:13, "Durumdara" wrote:
>
> "cached plan must not change result type"
As far as I remember, this kind of errors you can get from a prepared
statement execution, when the result type of it was changed (as in your
case by adding a column to a table that provides the data for a prep
Dear Members!
At Friday one of our clients got this error:
"cached plan must not change result type"
He restarted the application and the problem vanished.
We used PGDAC to access the database.
Firstly we didn't know nothing about this kind of error.
But later we realized that somebod
I install postgres 9.6.5 on CentOS 6.8.
However, i am not able to init the database due to the following error.
A bug
(http://www.postgresql-archive.org/BUG-8139-initdb-Misleading-error-message-when-current-user-not-in-etc-passwd-td5754618.html)
was reported with similar problem with but that was
It seems im missing some References but I don't know where to add them.
Here is my Error Code while using $source/configure --host=x86_64-w64-mingw32 --prefix=$dist && make && make install:
x86_64-w64-mingw32-gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -W
Re: Harry Ambrose 2017-08-25
> Hi All,
>
> Sorry to open this can of worms again. However, we are still struggling
> with this issue across quite a large amount of our estate.
Hi,
we've just seen exactly this error on a customer database running
9.5.3 (postgresql95.x86_64 9.5.3-2PGDG.rhel6). L
Hi All,
Sorry to open this can of worms again. However, we are still struggling
with this issue across quite a large amount of our estate.
>From doing some further research I stumbled across the following which
seems to sum up what we are seeing quite well...
http://grokbase.com/t/postgresql/pgs
On Wed, Aug 9, 2017 at 6:27 AM, ADSJ (Adam Sjøgren) wrote:
> On 2017-06-21 Adam Sjøgren wrote:
>
>> Adam Sjøgren wrote:
>
>>> Meanwhile, I can report that I have upgraded from 9.3.14 to 9.3.17 and
>>> the errors keep appearing the log.
>
> Just to close this, for the record: We haven't seen the
Unfortunately we still see it frequently :(
On 9 August 2017 at 14:29, Achilleas Mantzios
wrote:
> On 09/08/2017 15:27, ADSJ (Adam Sjøgren) wrote:
>
>> On 2017-06-21 Adam Sjøgren wrote:
>>
>> Adam Sjøgren wrote:
>>>
Meanwhile, I can report that I have upgraded from 9.3.14 to 9.3.17 and
>>
On 09/08/2017 15:27, ADSJ (Adam Sjøgren) wrote:
On 2017-06-21 Adam Sjøgren wrote:
Adam Sjøgren wrote:
Meanwhile, I can report that I have upgraded from 9.3.14 to 9.3.17 and
the errors keep appearing the log.
Just to close this, for the record: We haven't seen the errors since
2017-06-30. We
On 2017-06-21 Adam Sjøgren wrote:
> Adam Sjøgren wrote:
>> Meanwhile, I can report that I have upgraded from 9.3.14 to 9.3.17 and
>> the errors keep appearing the log.
Just to close this, for the record: We haven't seen the errors since
2017-06-30. We upgraded to 9.3.17 (latest 9.3 point-relea
Thank you Adrian, with \sf+ words_skip_game(integer, integer) the line 85
was correct
On 06/26/2017 01:10 PM, Paul A Jungwirth wrote:
On Mon, Jun 26, 2017 at 12:47 PM, Adrian Klaver
wrote:
On 06/26/2017 12:03 PM, Paul Jungwirth wrote:
Perhaps
you should see what is line 85 when you do `\sf words_skip_game` (rather
than line 85 in your own source code).
Or easier yet:
https:/
On 06/26/2017 01:10 PM, Paul A Jungwirth wrote:
On Mon, Jun 26, 2017 at 12:47 PM, Adrian Klaver
wrote:
On 06/26/2017 12:03 PM, Paul Jungwirth wrote:
Perhaps
you should see what is line 85 when you do `\sf words_skip_game` (rather
than line 85 in your own source code).
Or easier yet:
https:/
On Mon, Jun 26, 2017 at 12:47 PM, Adrian Klaver
wrote:
> On 06/26/2017 12:03 PM, Paul Jungwirth wrote:
>> Perhaps
>> you should see what is line 85 when you do `\sf words_skip_game` (rather
>> than line 85 in your own source code).
>
> Or easier yet:
>
> https://www.postgresql.org/docs/9.5/static/
On 06/26/2017 12:03 PM, Paul Jungwirth wrote:
On 06/26/2017 11:21 AM, Alexander Farber wrote:
The error message returned by
the database is rather cryptic:
words=> select * from words_skip_game(1, 1);
ERROR: query returned no rows
CONTEXT: PL/pgSQL function words_skip_game(integer,integer) li
On 06/26/2017 11:21 AM, Alexander Farber wrote:
The error message returned by
the database is rather cryptic:
words=> select * from words_skip_game(1, 1);
ERROR: query returned no rows
CONTEXT: PL/pgSQL function words_skip_game(integer,integer) line 85 at
SQL statement
When I look at my sourc
In my case _opponent was NULL and there are no records in words_users with
PK uid being NULL... so that was the reason.
Thank you
Hi again,
On Mon, Jun 26, 2017 at 8:21 PM, Alexander Farber <
alexander.far...@gmail.com> wrote:
>
> words=> select * from words_skip_game(1, 1);
> ERROR: query returned no rows
> CONTEXT: PL/pgSQL function words_skip_game(integer,integer) line 85 at
> SQL statement
>
> When I look at my source
On Mon, Jun 26, 2017 at 8:39 PM, Moreno Andreo
wrote:
> Il 26/06/2017 20:21, Alexander Farber ha scritto:
>
>>
>> RETURNING
>> player1,
>> score2,
>> score1
>> INTO
>> _
Il 26/06/2017 20:21, Alexander Farber ha scritto:
RETURNING
player1,
score2,
score1
INTO
_opponent,
_score1, -- the line 85
Good evening,
with PostgreSQL 9.5 I have extended a larger custom function, which has
worked well before and my problem is that the error message returned by the
database is rather cryptic:
words=> select * from words_skip_game(1, 1);
ERROR: query returned no rows
CONTEXT: PL/pgSQL function wor
Hi Everyone,
Still trying to fathom this one. I have added quite a few log lines to a
copy of 9.4.12 and compiled it hoping to find the fault.
Below is from the log (at DEBUG5). Apologies for my name in the log lines,
it was the easiest way to grep them specifically I also apologise that its
a bi
On 06/22/2017 10:05 AM, Jim Longwill wrote:
Ok. Thank you for the input. I do see the 'Description' of plpgsql
there. So, if I can determine the source table(s) of this information
perhaps I could delete that particular value.I tried the following
as per documentation:
COMMENT ON
On 06/21/2017 05:30 PM, Adrian Klaver wrote:
On 06/21/2017 05:06 PM, Jim Longwill wrote:
On 06/21/2017 01:21 PM, David G. Johnston wrote:
On Wed, Jun 21, 2017 at 1:10 PM, Jim Longwill
wrote:
rdev1=# \dd
Object descriptions
Schema | Name | Object | Description
+--+---
On 06/21/2017 05:06 PM, Jim Longwill wrote:
On 06/21/2017 01:21 PM, David G. Johnston wrote:
On Wed, Jun 21, 2017 at 1:10 PM, Jim Longwill
wrote:
rdev1=# \dd
Object descriptions
Schema | Name | Object | Description
+--++-
(0 rows)
Nothing user cre
On 06/21/2017 01:21 PM, David G. Johnston wrote:
On Wed, Jun 21, 2017 at 1:10 PM, Jim Longwill wrote:
rdev1=# \dd
Object descriptions
Schema | Name | Object | Description
+--++-
(0 rows)
Nothing user created has comments by default. \dd only shows
On Wed, Jun 21, 2017 at 1:10 PM, Jim Longwill wrote:
> rdev1=# \dd
> Object descriptions
> Schema | Name | Object | Description
> +--++-
> (0 rows)
Nothing user created has comments by default. \dd only shows a very
limited subset of user created object
On Wed, Jun 21, 2017 at 1:10 PM, Jim Longwill wrote:
> Given this, I wonder how we can avoid this 'error' situation .. short of
> giving SUPERUSER
> role to rradmin? I tried just removing the '-v' flag from pg_restore,
> but the error is
> still put in the log file (but nothing else is).
On 06/21/2017 11:05 AM, Jerry Sievers wrote:
Jim Longwill writes:
We have a (Linux CentOS) server, and one Postgres installation (v9.5).
We have long been experiencing an error when doing a 'pg_restore'
database build from a tar
file. Our procedure is as follows (err. is just after start o
Jim Longwill writes:
> We have a (Linux CentOS) server, and one Postgres installation (v9.5).
>
> We have long been experiencing an error when doing a 'pg_restore'
> database build from a tar
> file. Our procedure is as follows (err. is just after start of
> restoring our schema 'rradmin'):
>
>
We have a (Linux CentOS) server, and one Postgres installation (v9.5).
We have long been experiencing an error when doing a 'pg_restore'
database build from a tar
file. Our procedure is as follows (err. is just after start of
restoring our schema 'rradmin'):
First, an export is done to a .ta
Adam Sjøgren wrote:
> Meanwhile, I can report that I have upgraded from 9.3.14 to 9.3.17 and
> the errors keep appearing the log.
Just a quick update with more observations:
All the errors in the postgres.log from one of the tables are triggered
by a stored procedure that gathers data to put in
On Tue, Jun 20, 2017 at 11:12 AM, Computer Study
wrote:
> The UI application is to add/remove some permissions through a listbox for
> a certain user. For any add/remove, it will first delete all records for
> this certain user in the table, then insert the values chose from UI.
>
> In my code sn
Thanks Tom.
The version of Postgres is: 9.4.7
The UI application is to add/remove some permissions through a listbox for
a certain user. For any add/remove, it will first delete all records for
this certain user in the table, then insert the values chose from UI.
In my code snippet, it first ex
Computer Study writes:
> I am working on a project of DB migration from Oracle to Postgres. The
> application is working well with Oracle. But when switch to Postgres, some
> SQL executionss couldn't finish and got an error like:
> FATAL: DefineSavepoint: unexpected state STARTED
> STATEMENT: SAV
Hi,
I am working on a project of DB migration from Oracle to Postgres. The
application is working well with Oracle. But when switch to Postgres, some
SQL executionss couldn't finish and got an error like:
FATAL: DefineSavepoint: unexpected state STARTED
STATEMENT: SAVEPOINT_per_query_svp;DEALLOCA
Good evening everyone,
I apologize for the delay in replying and that you had to "reverse
engineer" my question.
This turned out indeed to be a special char problem.
On MBA with macOS Sierra 10.12.5 I am using Postgres 9.5.4.1 of
postgresapp.com.
At the psql prompt I had copy-pasted:
words=> S
Harry Ambrose writes:
> Not sure whether its relevant or not, however upon adding an ANALYSE before
> the second vacuum the issue has not presented when testing. I have managed
> 95 cycles thus far.
I'm still unable to reproduce :-( --- I ran about two dozen cycles
overnight with no sign of troub
Hi,
Not sure whether its relevant or not, however upon adding an ANALYSE before
the second vacuum the issue has not presented when testing. I have managed
95 cycles thus far.
BEGIN;
CREATE TABLE x (id BIGSERIAL PRIMARY KEY, payload1 VARCHAR, payload2
VARCHAR, payload3 VARCHAR, payload4 BIGINT, pa
On 06/12/2017 01:03 PM, Alexander Farber wrote:
Good evening!
Why does PostgreSQL 9.5.4 print the error:
LOG: execute : SELECT out_uid AS uid, out_fcm AS fcm,
out_apns AS apns, out_sns AS sns, out_note AS note FROM
words_resign_game($1::int, $2::int)
DETAIL: parameters: $1 = '2', $
On Mon, Jun 12, 2017 at 4:28 PM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Mon, Jun 12, 2017 at 1:03 PM, Alexander Farber <
> alexander.far...@gmail.com> wrote:
>
>> ERROR: type " " does not exist at character 149
>>
>
> Nothing shown would explain what you are seeing. Of cour
On Mon, Jun 12, 2017 at 1:03 PM, Alexander Farber <
alexander.far...@gmail.com> wrote:
> ERROR: type " " does not exist at character 149
>
Nothing shown would explain what you are seeing. Of course, white-space
issues are really hard to communicate via email.
As a brute-force suggestion I'd s
Alexander Farber writes:
> Why does PostgreSQL 9.5.4 print the error:
> ERROR: type " " does not exist at character 149
Hmph. Works for me, after reverse-engineering some tables and sample
data. Maybe your actual function text contains some non-breaking spaces,
or other weird stuff that didn't
Good evening!
Why does PostgreSQL 9.5.4 print the error:
LOG: execute : SELECT out_uid AS uid, out_fcm AS fcm,
out_apns AS apns, out_sns AS sns, out_note AS note FROM
words_resign_game($1::int, $2::int)
DETAIL: parameters: $1 = '2', $2 = '1'
ERROR: type " " does not exist at character 1
Hi,
BTW, how do you get that jar to make the test table on a non-default
> tablespace? Or are you just putting the whole test DB on a tablespace?
>
> regards, tom lane
>
I have been putting the whole database on a tablespace. It seemed easier
than modifying the jar.
Many
Harry Ambrose writes:
> - Custom tablespaces (where the errors occur) sat on 4 disk RAID-10 (ext3
> filesystem).
BTW, how do you get that jar to make the test table on a non-default
tablespace? Or are you just putting the whole test DB on a tablespace?
regards, tom lane
Achilleas Mantzios writes:
> After 2 full attempts, (and after bringing my poor - old workstation to its
> knees) it still does not produce the supposed ERROR :
Yeah, I've had little luck reproducing it either. However, I noticed a
few messages back that Harry is testing against a master/slave
It seems to be very hit and miss...
The below is from the machine described in this thread running PostgreSQL
9.4.10:
update 10
update 12
update 14
update 16
update 18
Update all
Vacuum
org.postgresql.util.PSQLException: ERROR: unexpected chunk number 2285
(expected 0)
Hi,
pls tell me, I am currently running 2nd run in my box, (New attempt 2), and
> its in the "Attempting vacuum" phase.
> What is it supposed to do next?
> I got no errors , it has gotten my machine to its knees.
>
The jar has an endless while loop. Thus please kill the PID when you are
done test
On 12/06/2017 10:46, Harry Ambrose wrote:
Hi,
> Their suggestion is to upload to Google Drive. That or use a third party
site, like Dropbox.
I have uploaded the jar to dropbox, link below (please let me know if you have
any issues downloading):
https://www.dropbox.com/s/96vm465i7rwhcf8/toast
Hi,
> Their suggestion is to upload to Google Drive. That or use a third party
site, like Dropbox.
I have uploaded the jar to dropbox, link below (please let me know if you
have any issues downloading):
https://www.dropbox.com/s/96vm465i7rwhcf8/toast-corrupter-aio.jar?dl=0
> So I guess you run
Alvaro Herrera wrote:
> ADSJ (Adam Sjøgren) wrote:
>
>> Our database has started reporting errors like this:
>>
>> 2017-05-31 13:48:10 CEST ERROR: unexpected chunk number 0 (expected 1)
>> for toast value 14242189 in pg_toast_10919630
> Does the problem still reproduce if you revert commit
On 09/06/2017 19:02, Harry Ambrose wrote:
Hi,
No error messages found.
- is your RAM ECC? Did you run any memtest?
Yes, memory is ECC. No error messages found.
So I guess you run memtest86+ and it reported that your memory is indeed ECC
and also that it is working properly?
Best wishes,
On 06/11/2017 08:34 AM, Tom Lane wrote:
Alvaro Herrera writes:
I'm unable to run this file. Maybe it was corrupted in transit, given
that it was considered to be text.
My copy came through fine, so I tried to forward it to you off-list,
but gmail rejected it as a possible security hazard. D
Alvaro Herrera writes:
> I'm unable to run this file. Maybe it was corrupted in transit, given
> that it was considered to be text.
My copy came through fine, so I tried to forward it to you off-list,
but gmail rejected it as a possible security hazard. Do you know
which binary mime types they
Harry Ambrose wrote:
> Hi,
>
> Please find the jar attached (renamed with a .txt extension as I know some
> email services deem jars a security issue).
>
> The jar accepts the following arguments:
>
> $1 = host
> $2 = database
> $3 = username
> $4 = password
> $5 = port
>
> It returns its loggi
ADSJ (Adam Sjøgren) wrote:
> Our database has started reporting errors like this:
>
> 2017-05-31 13:48:10 CEST ERROR: unexpected chunk number 0 (expected 1) for
> toast value 14242189 in pg_toast_10919630
Does the problem still reproduce if you revert commit
6c243f90ab6904f27fa990f1f3261e1d09
Hi,
Please find the jar attached (renamed with a .txt extension as I know some
email services deem jars a security issue).
The jar accepts the following arguments:
$1 = host
$2 = database
$3 = username
$4 = password
$5 = port
It returns its logging to STDOUT. Please let me know if you require f
Hi,
Please find the jar attached (renamed with a .txt extension as I know some
email services deem jars a security issue).
The jar accepts the following arguments:
$1 = host
$2 = database
$3 = username
$4 = password
$5 = port
It returns its logging to STDOUT. Please let me know if you require f
Robert Lakes writes:
> I am new to postgress and I am trying to write my first function to insert,
> update or delete and trap errors as a result of the table not existing ,
> the columns not exist or if any other error simply pass back the sqlstate
Please do not hijack an existing thread to ask
Ha guys,
I am new to postgress and I am trying to write my first function to insert,
update or delete and trap errors as a result of the table not existing ,
the columns not exist or if any other error simply pass back the sqlstate
here's my code can you help
CREATE OR REPLACE FUNCTION listings_aud
Hi,
Maybe you could give some info on :
> - your ext3 mkfs and mount options (journal, barriers, etc)
>
/etc/fstab details below:
LABEL=/var/lib/pgsql/var/lib/pgsql ext3defaults
1 2
LABEL=/tablespace1 /tablespace1ext3defaults
1 2
LABEL=/tabl
On 09/06/2017 14:44, Harry Ambrose wrote:
Hi Tom,
Thanks for attempting to replicate the issue.
Anyway, the bad news is I couldn't reproduce the problem then and I can't
now. I don't know if it's a timing issue or if there's something critical
about configuration that I'm not dupli
Hi Tom,
Thanks for attempting to replicate the issue.
Anyway, the bad news is I couldn't reproduce the problem then and I can't
> now. I don't know if it's a timing issue or if there's something critical
> about configuration that I'm not duplicating. Can you explain what sort
> of platform you
Harry Ambrose writes:
> Please find the jar attached (renamed with a .txt extension as I know some
> email services deem jars a security issue).
Hmm, the output from this script reminds me quite a lot of one I was
sent in connection with bug #1 awhile back:
https://www.postgresql.org/message-
On 06/08/2017 08:13 AM, ADSJ (Adam Sjøgren) wrote:
Achilleas writes:
Anyone has a handy little script lying around?
http://www.databasesoup.com/2013/10/de-corrupting-toast-tables.html
Thanks for the response!
Adam
--
Adrian Klaver
adrian.kla...@aklaver.com
--
Sent via pg
Harry writes:
> The second vacuum causes an ERROR identical to that you are reporting
> below (unexpected chunk number n (expected n) for toast value...).
> However it may take up to ten attempts to replicate it.
Interesting.
> Out of interest, are you using any tablespaces other than pg_default
Achilleas writes:
> First try to find which tables those toast relations refer to :
> select 10919630::regclass , 10920100::regclass ;
> Are those critical tables? Can you restore them somehow?
They are our two big tables, containing the bulk of our data (one with
168M rows, the other with 320M r
Harry Ambrose writes:
> Tom - I can provide a jar that I have been using to replicate the issue.
> Whats the best transport method to send it over?
If it's not enormous, just send it as an email attachment.
regards, tom lane
--
Sent via pgsql-general mailing list (pgs
Hi,
Thanks for the responses.
> "One lesson I learned from the BSD camp when dealing with random freezes and
> panics : when all else fails to give an answer it is time to start blaming my
> hardware. Are those tablespaces on any cheap SSD's ?”
The tablespaces are not sat on SSD’s. Something I
Harry Ambrose writes:
> I have been following the updates to the 9.4 branch hoping a fix will appear,
> but sadly no luck yet. I have manually replicated the issue on 9.4.4, 9.4.10
> and 9.4.12. My replication steps are:
This is a very interesting report, but you didn't actually provide a
repro
On 07/06/2017 17:49, Harry Ambrose wrote:
Hi,
Out of interest, are you using any tablespaces other than pg_default? I can
only replicate the issue when using separately mounted tablespaces.
One lesson I learned from the BSD camp when dealing with random freezes and panics : when all else fails t
Hi,
I too have been experiencing this with a busy PostgreSQL instance.
I have been following the updates to the 9.4 branch hoping a fix will appear,
but sadly no luck yet. I have manually replicated the issue on 9.4.4, 9.4.10
and 9.4.12. My replication steps are:
BEGIN;
CREATE TABLE x (id BIGS
On 07/06/2017 16:33, ADSJ (Adam Sjøgren) wrote:
Our database has started reporting errors like this:
2017-05-31 13:48:10 CEST ERROR: unexpected chunk number 0 (expected 1) for
toast value 14242189 in pg_toast_10919630
...
2017-06-01 11:06:56 CEST ERROR: unexpected chunk number 0
Our database has started reporting errors like this:
2017-05-31 13:48:10 CEST ERROR: unexpected chunk number 0 (expected 1) for
toast value 14242189 in pg_toast_10919630
...
2017-06-01 11:06:56 CEST ERROR: unexpected chunk number 0 (expected 1) for
toast value 19573520 in pg_toast_10
On 2017-05-18 21:48, Rob Brucks wrote:
Hello Everyone,
I am unable to figure out how the trigger was able to successfully
create the table, but then fail creating the index. I would have
expected one thread to "win" and create both the table and index, but
other threads would fail when creating
On Thu, May 18, 2017 at 1:46 PM, John R Pierce wrote:
> On 5/18/2017 1:40 PM, Andrew Kerber wrote:
>
>> It appears to me you might be making this a lot more difficult than
>> necessary. Why not just pre-create the required partitions daily or weekly
>> or monthly? Or do you have a requirement tha
On 5/18/2017 1:40 PM, Andrew Kerber wrote:
It appears to me you might be making this a lot more difficult than
necessary. Why not just pre-create the required partitions daily or
weekly or monthly? Or do you have a requirement that a new partition
only be created the first time it is required?
t;
>
>
> Thanks,
>
> Rob
>
>
>
> *From: *"David G. Johnston"
> *Date: *Thursday, May 18, 2017 at 3:31 PM
> *To: *Rob Brucks
> *Cc: *"pgsql-general@postgresql.org"
> *Subject: *Re: [GENERAL] Error that shouldn't happen?
>
>
>
&
On Thu, May 18, 2017 at 1:39 PM, Rob Brucks
wrote:
> My point is how did two concurrent threads successfully create the same
> table?
>
You seem to not be understanding that "CREATE TABLE IF NOT EXISTS" can
succeed without actually creating a table...
David J.
It appears to me you might be making this a lot more difficult than
necessary. Why not just pre-create the required partitions daily or weekly
or monthly? Or do you have a requirement that a new partition only be
created the first time it is required?
On Thu, May 18, 2017 at 3:31 PM, David G. John
Postgres skipped checking for duplicate tables due to some
timing issue. I don't want my DB to ending up hosed by something like that.
Thanks,
Rob
From: "David G. Johnston"
Date: Thursday, May 18, 2017 at 3:31 PM
To: Rob Brucks
Cc: "pgsql-general@postgresql.org"
Sub
On Thu, May 18, 2017 at 1:18 PM, Rob Brucks
wrote:
> According to this post, adding "if not exists" won't really help for race
> conditions.
>
>
>
> "The bottom line is that CREATE TABLE IF NOT EXISTS doesn't pretend to
>
> handle concurrency issues any better than regular old CREATE TABLE,
>
> w
ntion on the create table statement.
Thanks,
Rob
From: "David G. Johnston"
Date: Thursday, May 18, 2017 at 3:05 PM
To: Rob Brucks
Cc: "pgsql-general@postgresql.org"
Subject: Re: [GENERAL] Error that shouldn't happen?
On Thu, May 18, 2017 at 12:48 PM, Rob Brucks
mailto
On Thu, May 18, 2017 at 12:48 PM, Rob Brucks
wrote:
> I am unable to figure out how the trigger was able to successfully create
> the table, but then fail creating the index. I would have expected one
> thread to "win" and create both the table and index, but other threads
> would fail when crea
Hello Everyone,
I've run into a strange error on the PostgreSQL 9.5.4 DB we use for our Zabbix
Server. I implemented auto-partitioning based on the design from this wiki
article:
https://www.zabbix.org/wiki/Docs/howto/zabbix2_postgresql_autopartitioning
I implemented auto-partitioning for the
Sachin Srivastava writes:
> Dear Team,
>
> Please suggest why we are getting the below error in our PostgreSQL
> DB log.
>
> We are using postgresql version = 9.2
>
>
> ERROR: prepared transaction with identifier "131077_AP//
I dont have such an ancient version of Pg to test with bu
On Friday, April 28, 2017, Sachin Srivastava
wrote:
>
> Please suggest why we are getting the below error in our PostgreSQL DB log.
>
> ERROR: prepared transaction with identifier "131077_AP//
> CqqfIep65ipZAmdpAAIcgjE=_AP//CqqfIep65ipZAmdpAAIciwAA"
> does not exis
I have already tuned below parameters as
max_prepared_transactions = 500
max_connection = 2000
Regards,
SSR
On Sat, Apr 29, 2017 at 12:15 AM, Sachin Srivastava wrote:
> Dear Team,
>
> Please suggest why we are getting the below error in our PostgreSQL DB log.
>
> We are using postgresql v
Dear Team,
Please suggest why we are getting the below error in our PostgreSQL DB log.
We are using postgresql version = 9.2
ERROR: prepared transaction with identifier
"131077_AP//CqqfIep65ipZAmdpAAIcgjE=_AP//CqqfIep65ipZAmdpAAIciwAA"
does not exist
STATEMENT:
Hi Adrian,
This suggestion helped to resolve the problem. Thanks a lot for your help.
On Sat, Apr 15, 2017 at 8:02 PM, Adrian Klaver
wrote:
> On 04/15/2017 11:25 AM, John R Pierce wrote:
>
>> On 4/15/2017 10:49 AM, Adrian Klaver wrote:
>>
>>>
>>> Probably going to involve dealing with ldconfig.
Noted
Something I meant to refer to earlier, it is considered bad etiquette to
> cross post to multiple lists. It means in this case I have to remember to
> drop the postgis list from my replies as I am not a member of that list and
> I get a rejection notice if I forget.
Hi,
On Wed, 2017-04-12 at 16:10 -0700, John R Pierce wrote:
> if you install those packages from the yum repository, doesn't postgis
> include raster support?
It does.
Regards,
--
Devrim Gündüz
EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engine
On 04/15/2017 11:25 AM, John R Pierce wrote:
On 4/15/2017 10:49 AM, Adrian Klaver wrote:
Probably going to involve dealing with ldconfig.
Look in /etc/ld.so.conf and see if the directory that contains
libproj.so.12 is in there?
the catch-22 is, /etc/ld.so.conf is a global thing, and this guy
On 4/15/2017 10:49 AM, Adrian Klaver wrote:
Probably going to involve dealing with ldconfig.
Look in /etc/ld.so.conf and see if the directory that contains
libproj.so.12 is in there?
the catch-22 is, /etc/ld.so.conf is a global thing, and this guy is
building all his stuff to run under his
On 04/14/2017 12:20 PM, Osahon Oduware wrote:
Hi Adrian,
Something I meant to refer to earlier, it is considered bad etiquette to
cross post to multiple lists. It means in this case I have to remember
to drop the postgis list from my replies as I am not a member of that
list and I get a rej
Hi Adrian,
I installed Proj from source and I can confirm that the file libproj.so.12
is in its lib folder.
I have not been able to confirm if it is linked to postgis-2.3.so as I am
away for Easter holiday.
Just in case, how do I do the linking of libproj.so.12 to postgis-2.3.so as
I believe thi
On 04/13/2017 07:54 AM, Osahon Oduware wrote:
Hi Adrian,
Thanks for your help so far. This is the output of the PostGIS
configuration:
-- Compiler Info -
C compiler: gcc -g -O2
SQL preprocessor: /usr/bin/cpp -traditional-cpp -w -P
-- Depen
1 - 100 of 2198 matches
Mail list logo
