Steve Haresnape schrieb am 15.03.2019 um 00:06:
> I'm porting a sql server database to postgresql 9.6. My camelCase
> identifiers are having their humps removed. This is disconcerting and
> sad.
>
> Is there a cure for this?
>
> I don't want to quote my identifiers unless I have to.
You don't ne
On Thursday, March 14, 2019, M Tarkeshwar Rao
wrote:
>
> Facing issue in using special characters. We are trying to insert records
> to a remote Postgres Server and our application not able to perform this
> because of errors.
>
> It seems that issue is because of the special characters that has b
Hi all,
Facing issue in using special characters. We are trying to insert records to a
remote Postgres Server and our application not able to perform this because of
errors.
It seems that issue is because of the special characters that has been used in
one of the field of a row.
Regards
Tarkes
On 3/14/19 7:12 PM, fuzk wrote:
When I set max_parallel_workers_per_gather=0, the select statement can
execute successfully. The problem has been solved. Thank you all very
much. Alan
Well the problem has been hidden, not solved. It did establish that
invoking parallel query has something
On Fri, Mar 15, 2019 at 12:10:59AM +0800, Mike Yeap wrote:
> Hi Noah, below is the output from one of the servers having this issue:
>
> $ echo "select pg_backend_pid(); load 'dblink'; select pg_sleep(100)" | psql
> -X &
> [1] 9731
>
> $ select pg_backend_pid(); load 'dblink'; select pg_sleep(10
Thomas Munro writes:
> A fast way to find out would be to get one of these people who can
> reproduce the problem to recompile PostgreSQL with that error changed
> to a PANIC, and examine the resulting smoldering core. (Someone had a
> proposal to make PostgreSQL errors optionally dump the functi
On Thu, Mar 14, 2019 at 4:07 PM Steve Haresnape
wrote:
>
> I'm porting a sql server database to postgresql 9.6. My camelCase identifiers
> are having their humps removed. This is disconcerting and sad.
>
> Is there a cure for this?
No
>I don't want to quote my identifiers unless I have to.
Pos
I'm porting a sql server database to postgresql 9.6. My camelCase
identifiers are having their humps removed. This is disconcerting and sad.
Is there a cure for this?
I don't want to quote my identifiers unless I have to. I don't want to use
underscores. Everywhere else I write code I use camel c
On 3/14/19 11:45 AM, Perumal Raj wrote:
Please reply to list also.
Ccing list.
Thanks Adrian for the reply,
Yes , i went through the document.
My Only Worry is , Will i hit performance issue once i reach 200M
Age(default) even i have only static table.
If is truly static then there will be
On Fri, Mar 15, 2019 at 6:09 AM Julien Rouhaud wrote:
> > > > https://trac.osgeo.org/postgis/ticket/4129
> I also tried to reproduce on latest postgis 2.4 / pg11 with anything
> even slightly related to what could call GetLatestSnapshot() with
> force_parallel_mode enabled and parallel_leader_pa
>
> *autovacuum_analyze_threshold*
> *autovacuum_analyze_scale_factor*
>
Changing these will impact how often the table is analyzed based on the
rough count of changed rows. You may want to adjust autovacuum settings as
well so that dead space can be reused.
> *default_statistics_target*
>
Increa
Hi
We have a busy postgres 10 Db with a principal table that holds about 15
million active rows and has about 90M Inserts|Updates|Deletes a day.
All performs well, except a small number of monitoring SQL statements of the
nature
select code, max(timestamp) from mainTable group by code;
After
On Thu, Mar 14, 2019 at 4:59 PM Paul Ramsey wrote:
>
> On Thu, Mar 14, 2019 at 8:43 AM Julien Rouhaud wrote:
> >
> > On Thu, Mar 14, 2019 at 3:25 PM Adrian Klaver
> > wrote:
> > >
> > > On 3/14/19 6:14 AM, Julien Rouhaud wrote:
> > > > On Thu, Mar 14, 2019 at 1:20 PM fuzk wrote:
> > > >>
> > >
Hi Noah, below is the output from one of the servers having this issue:
$ echo "select pg_backend_pid(); load 'dblink'; select pg_sleep(100)" |
psql -X &
[1] 9731
$ select pg_backend_pid(); load 'dblink'; select pg_sleep(100)
pg_backend_pid
9732
(1 row)
LOAD
$ gdb -
On Thu, Mar 14, 2019 at 8:43 AM Julien Rouhaud wrote:
>
> On Thu, Mar 14, 2019 at 3:25 PM Adrian Klaver
> wrote:
> >
> > On 3/14/19 6:14 AM, Julien Rouhaud wrote:
> > > On Thu, Mar 14, 2019 at 1:20 PM fuzk wrote:
> > >>
> > >> Dear Adrian,
> > >>
> > >> My setting is as following.
> > >>
> > >>
On Thu, Mar 14, 2019 at 3:25 PM Adrian Klaver wrote:
>
> On 3/14/19 6:14 AM, Julien Rouhaud wrote:
> > On Thu, Mar 14, 2019 at 1:20 PM fuzk wrote:
> >>
> >> Dear Adrian,
> >>
> >> My setting is as following.
> >>
> >> max_parallel_workers_per_gather=32
> >>
> >> I am looking forward to hearing fr
I don't find a clear mention in the docs of superuser processes that are
exempt from counting toward superuser_reserved_connections. So I would
think that it's possible that postgres autovac workers ought to count
toward that. Am I wrong about that? I actually have the same question
about pglogi
I found this error in queries generated from templates query36.tpl,
query70.tpl, and query86.tpl. The problem is, lochierarchy is an alias
defined in the SELECT statement, and the alias isn't being recognized in
the CASE statement. PostgreSQL does not allow a column alias to be
referenced in a CA
On 3/13/19 10:54 PM, fuzk wrote:
Dear Adrian,
My setting is as following.
max_parallel_workers_per_gather=32
Not sure if it is possible without affecting other operations, but you
could set the above to 0 to temporarily disable parallel queries and see
if that eliminates the error.
Also s
On 3/14/19 6:14 AM, Julien Rouhaud wrote:
On Thu, Mar 14, 2019 at 1:20 PM fuzk wrote:
Dear Adrian,
My setting is as following.
max_parallel_workers_per_gather=32
I am looking forward to hearing from you.
What version of postgres and what version of postgis are you using ?
At 2019-03-13
On 3/14/19 5:31 AM, Edson Carlos Ericksson Richter wrote:
Em 14/03/2019 09:05, Angélica Barcellos escreveu:
Bom dia. Recebo constantemente os e-mails,tem como retirar o meu
e-mail dessa lista. Não quero receber mais nada. OBRIGADO
Angélica Barcelos Cardoso
Hello, Angelica.
I'm not the lis
On Thu, Mar 14, 2019 at 1:20 PM fuzk wrote:
>
> Dear Adrian,
>
> My setting is as following.
>
> max_parallel_workers_per_gather=32
>
> I am looking forward to hearing from you.
What version of postgres and what version of postgis are you using ?
> At 2019-03-13 22:31:11, "Adrian Klaver" wrote:
Em 14/03/2019 09:05, Angélica Barcellos escreveu:
Bom dia. Recebo constantemente os e-mails,tem como retirar o meu
e-mail dessa lista. Não quero receber mais nada. OBRIGADO
Angélica Barcelos Cardoso
Hello, Angelica.
I'm not the list administrator, but I believe that you will have to run
Dear Adrian,
My setting is as following.
max_parallel_workers_per_gather=32
I am looking forward to hearing from you.
Many thanks
Alan.
At 2019-03-13 22:31:11, "Adrian Klaver" wrote:
>On 3/12/19 7:54 PM, fuzk wrote:
>> Dear Sir/Madam
>>
>> I got an error when I execute the followi
I had been wondering as to where one can use BEFORE STATEMENT level
trigger, more so because one does not know (access) what rows are getting
affected. Only thing which comes to my mind is that if one wants to do
something at a table-level, then this trigger can be used; this is quite
unusual thoug
Bom dia. Recebo constantemente os e-mails,tem como retirar o meu e-mail dessa
lista. Não quero receber mais nada. OBRIGADO
Angélica Barcelos Cardoso
I have multiple warm standby replicas of PostgreSQL 11, used by analytics.
Some of the databases are not very active and I have a problem to figure
out if the recovery is in progress or actually there is nothing to recover
(because of master inactivity).
I set target time on replica like this:
rec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/3/19 5:15 pm, Michael Cassaniti wrote:
> > On 14/3/19 3:10 pm, Michael Paquier wrote: > > On Thu, Mar 14, 2019
at 02:59:38PM +1100, Michael Cassaniti wrote: >> I've got master/slave
replication setup between a few hosts. At any > >> point a s
Hello all !
There is the Ansible postgresql working group
https://github.com/ansible/community/wiki/PostgreSQL
that was created a couple of months ago (thanks Ansible engineers Dag Wieers
(@dagwieers) and John R. Barcker (@gundalow) for support).
Over the last 3 months we've added 4 new modul
29 matches
Mail list logo
