On Thu, Jun 21, 2018 at 04:50:38PM -0700, David G. Johnston wrote:
> Generally only actual bug fixes get back-patched; but I'd have to say
> this looks like it could easily be classified as one.
Everybody is against me here ;)
> Some comments on the patch itself:
>
> "recover up to the wanted re
On Thu, Jun 21, 2018 at 04:42:00PM -0400, Ravi Krishna wrote:
> Same here even though I use Mac mail. But it is not yahoo alone.
> Most of the web email clients have resorted to top posting. I miss
> the old days of Outlook Express which was so '>' friendly. I think
> Gmail allows '>' when you c
On Fri, Jun 22, 2018 at 11:22 AM, David Pacheco wrote:
> On Wed, Jun 20, 2018 at 10:35 AM, Jerry Jelinek
> wrote:
>> I have implemented a small change to allow WAL recycling to be disabled.
>> It is visible at:
>> https://cr.joyent.us/#/c/4263/
>>
>> I'd appreciate getting any feedback on this.
On Thu, Jun 21, 2018 at 4:26 PM, Vik Fearing
wrote:
> On 21/06/18 07:27, Michael Paquier wrote:
> > Attached is a patch which includes your suggestion. What do you think?
> > As that's an improvement, only HEAD would get that clarification.
>
> Say what? If the clarification applies to previous
On 21/06/18 07:27, Michael Paquier wrote:
> Attached is a patch which includes your suggestion. What do you think?
> As that's an improvement, only HEAD would get that clarification.
Say what? If the clarification applies to previous versions, as it
does, it should be backpatched. This isn't a
On Wed, Jun 20, 2018 at 10:35 AM, Jerry Jelinek
wrote:
> As Dave described in his original email on this topic, we'd like to avoid
> recycling WAL files since that can cause performance issues when we have a
> read-modify-write on a file that has dropped out of the cache.
>
> I have implemented a
On 06/21/2018 08:36 AM, Moreno Andreo wrote:
Hi,
while playing with pgcrypto I ran into a strange issue (postgresql
9.5.3 x86 on Windows 7)
Having a table with a field
dateofbirth text
I made the following sequence of SQL commands
update tbl_p set dateofbirth = pgp_sym_encrypt('2018-06-2
DiasCosta writes:
> This is the query plan for only 19684 rows.
I think you're getting a bad query plan, mostly as a result of two
factors:
* Poor row estimates. It looks like the bottom-most misestimations
are on temp tables, which makes me wonder whether you've ANALYZEd
those tables. Your ap
Hello David and Fabrízio,
The names of the tables and indexes differ from the original script.
Only the names.
This is the query plan for only 19684 rows.
I have another query running for around 3 rows, but it takes an
eternity to finish.
If it finishes in acceptable time I'll make it a
>
>
> >You should avoid top-posting on the Postgres lists, this is not the
> >usual style used by people around :)
>
> Will do, but Yahoo Mail! does not seem to like that, so I am typing the >
> myself
>
Same here even though I use Mac mail. But it is not yahoo alone.
Most of the web email c
Hi Michael
On Thursday, June 21, 2018, 7:28:13 AM GMT+2, Michael Paquier
wrote:
>You should avoid top-posting on the Postgres lists, this is not the
>usual style used by people around :)
Will do, but Yahoo Mail! does not seem to like that, so I am typing the > myself
>Attached is a pat
Hi,
while playing with pgcrypto I ran into a strange issue (postgresql
9.5.3 x86 on Windows 7)
Having a table with a field
dateofbirth text
I made the following sequence of SQL commands
update tbl_p set dateofbirth = pgp_sym_encrypt('2018-06-21', 'AES_KEY')
where codguid = '0001-0001-
As said, terminating a backend is the current way to kill a job.
An alternative if this is something you do often:
https://github.com/GoSimpleLLC/jpgAgent
jpgAgent supports terminating a job by issuing a NOTIFY command on the
correct channel like this: NOTIFY jpgagent_kill_job, 'job_id_here';
It w
Hi ,
That would work as long as the user name and password used to login into
> Access are also recognized by Postgres.
I created users in postgresql and connecting to database using windows
username and common password.
Thank you for help.
Best,
Luke
2018-06-21 15:33 GMT+02:00 Adrian Klaver
On 06/21/2018 01:33 AM, Łukasz Jarych wrote:
Hi Guys,
the best option here i think is to:
1. Create users login in Access
2. Use DSN-less odbc connection.
3. When user is login to Access i am taking password and using it in
postgresql BE.
That would work as long as the user name and password
On 06/21/2018 12:17 AM, Łukasz Jarych wrote:
Hmm one problem.
How to distinct value for specific user?
I created new table in postgresql and when user is login into system New
value is added to field "System_user".
But how to show postgresql database that should use the specific value
(for inp
Hi Shore,
Have a look at:
https://www.postgresql.org/docs/current/static/functions-admin.html
'pg_terminate_backend' is probably what you are looking for
regards,
fabio pardi
On 21/06/18 11:32, a wrote:
> Hi
>
> I'm using pgAdmin 4, pgAgent and postgresql 10 on windows server.
>
> I tried a
Hi
I'm using pgAdmin 4, pgAgent and postgresql 10 on windows server.
I tried a job but due to some reasons, its running long time. Is there a way
that I can terminate it ??
Thanks
Shore
Hi Guys,
the best option here i think is to:
1. Create users login in Access
2. Use DSN-less odbc connection.
3. When user is login to Access i am taking password and using it in
postgresql BE.
Best,
Luke
2018-06-21 9:17 GMT+02:00 Łukasz Jarych :
> Hmm one problem.
>
> How to distinct value fo
Hmm one problem.
How to distinct value for specific user?
I created new table in postgresql and when user is login into system New
value is added to field "System_user".
But how to show postgresql database that should use the specific value (for
inputing data user, not for others?).
Best,
Luke
2
20 matches
Mail list logo
