On 03/21/2014 05:29 PM, john.tiger wrote:
thks for quick comments - see below:
On 03/21/2014 06:00 PM, Adrian Klaver wrote:
On 03/21/2014 04:47 PM, john.tiger wrote:
9.3 install on debian jessie 64amd
sudo -u postgres psql => worked
alter user postgres with password 'password' => alter ro
On 03/21/2014 06:38 PM, john.tiger wrote:
On 03/21/2014 06:43 PM, Rodrigo Gonzalez wrote:
On 03/21/2014 09:29 PM, john.tiger wrote:
EDIT from @rodrigo
hmm, user postgres vs os postgres - okay understand what you mean but
how is this fixed ? or what is proper procedure ?
It depends on wh
On 03/21/2014 06:43 PM, Rodrigo Gonzalez wrote:
On 03/21/2014 09:29 PM, john.tiger wrote:
EDIT from @rodrigo
hmm, user postgres vs os postgres - okay understand what you mean but
how is this fixed ? or what is proper procedure ?
It depends on what you want to fix...
if you want to be abl
On 03/21/2014 09:29 PM, john.tiger wrote:
> EDIT from @rodrigo
>
> hmm, user postgres vs os postgres - okay understand what you mean but
> how is this fixed ? or what is proper procedure ?
>
It depends on what you want to fix...
if you want to be able to do su - postgres change its OS passwor
thks for quick comments - see below:
On 03/21/2014 06:00 PM, Adrian Klaver wrote:
On 03/21/2014 04:47 PM, john.tiger wrote:
9.3 install on debian jessie 64amd
sudo -u postgres psql => worked
alter user postgres with password 'password' => alter role
su - postgress
enter password => auth
On 03/21/2014 08:47 PM, john.tiger wrote:
> 9.3 install on debian jessie 64amd
>
> sudo -u postgres psql => worked
> alter user postgres with password 'password' => alter role
>
> su - postgress
> enter password => authentication failure
postgress or postgres?
The name is different, but in
On 03/21/2014 04:47 PM, john.tiger wrote:
9.3 install on debian jessie 64amd
sudo -u postgres psql => worked
alter user postgres with password 'password' => alter role
su - postgress
enter password => authentication failure
So did you really type postgress (note extra s) or is this just
9.3 install on debian jessie 64amd
sudo -u postgres psql => worked
alter user postgres with password 'password' => alter role
su - postgress
enter password => authentication failure
hba.conf edited to allow "trust" to local - shouldn't this be set up as
standard default ?
still authent
Surge 2014 dates are September 24-26, 2014; the CFP is open and the
deadline is March 31, 2014.
Thank you,
--Katherine
Hi All;
when I try to compile postgresql 9.3.4 I get the below errors, anyone
know if / which devel packages I need?
Thanks in advance
checking crypt.h usability... no
checking crypt.h presence... yes
configure: WARNING: crypt.h: present but cannot be compiled
configure: WARNING: crypt.h:
On Fri, 21 Mar 2014, Rich Shepard wrote:
psql -e -d template1 -f
/home/rshepard/data/database-backups/pg-9.0.5-2014-03-17.sql
Yep.
Now all databases are running on 9.3.4.
Thanks, all!
Rich
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your s
https://github.com/peak6/wallctl
Oops. I just renamed this to:
https://github.com/peak6/walctl
I didn't realize the repo was created named wallctl instead of walctl.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
stho...@optionshouse.com
Hello again,
Now that the open-source floodgates have been opened, I've been prepping
a couple of our applicable projects. This time, I've added this:
https://github.com/peak6/wallctl
It is a very simple PostgreSQL WAL management system that pushes or
pulls WAL files from a remote central st
Glenn Pierce wrote
> I cannot work out how to pass a literal for the array of timerange types.
> '{(15:11:21, 18:11:21)}'::timerange[] does not work for example.
> Also I can not pass NULL for this parameter I get
since NULL can take on any type if you pass it literally you have to specify
the typ
Hi there,
I was just wondering if anyone has some general advice for how to
ensure a schema migration for an application has exclusivity during
its run.
This is to avoid silly things like, if someone leaves an application
server running during migration the migration should be able to lock
someho
On Fri, 21 Mar 2014, Rich Shepard wrote:
1.) Start the new -9.4 version running.
It's now running.
2.) Run pg_restore on each database that's in the .sql file created by
pg_dumpall.
Will this work?
psql -e -d template1 -f
/home/rshepard/data/database-backups/pg-9.0.5-2014-03.17.sq
On Fri, 21 Mar 2014, Rich Shepard wrote:
I did a pg_dumpall before starting this process. If I can use pg_restore
on the running 9.4 will that convert locales and get the job done?
Let me be more specific. Can I get databases working again by doing these
steps?
1.) Start the new -9.4 vers
On Fri, 21 Mar 2014, Joshua D. Drake wrote:
If you want to use pg_upgrade, then you are going to have to dump your old
database, clean it to UTF-8 (with say iconv), then reimport it.
At that point you might as well just pull it into 9.3.
Joshua,
I did a pg_dumpall before starting this proc
On Fri, 21 Mar 2014, Sergey Konoplev wrote:
Drop your newly created 9.4 cluster dir and re-init it with C locale like this:
Sergey,
How do I drop the cluster? I've not had need to do this before.
initdb --locale=C -D ...
Do I want the former locale or the current one; does it make any
On 03/21/2014 09:34 AM, Rich Shepard wrote:
Postgresql-9.0.5 is installed in /usr/local/pgsql/ and -9.4's data/
subdirectory is installed in /var/lib/pgsql/9.4/ with the executable in
/usr/bin/.
Running pg_upgrade fails at the end because of a locale difference:
lc_ctype cluster values
On Fri, Mar 21, 2014 at 9:34 AM, Rich Shepard wrote:
> Postgresql-9.0.5 is installed in /usr/local/pgsql/ and -9.4's data/
> subdirectory is installed in /var/lib/pgsql/9.4/ with the executable in
> /usr/bin/.
>
> Running pg_upgrade fails at the end because of a locale difference:
>
> lc_ctype
Postgresql-9.0.5 is installed in /usr/local/pgsql/ and -9.4's data/
subdirectory is installed in /var/lib/pgsql/9.4/ with the executable in
/usr/bin/.
Running pg_upgrade fails at the end because of a locale difference:
lc_ctype cluster values do not match: old "C", new "en_US.UTF-8"
Failure
Hi
I am try to create a function that returns true if a timestamp is within
working hours.
The function will take the following parameters.
1, timestamp - The timestamp I want to check
2, days_of_week - An array of integers that tells us what days are work
days.
3, time_ranges - An array of my c
On Fri, Mar 21, 2014 at 2:46 AM, Granthana Biswas wrote:
> We don't have two-phase commit prepared transactions. During vacuum, along
> with this problem we are also facing streaming replication issue. Hundreds of
> xlogs are in ready state in pg_xlog/archive_status. Those are being copied
> ma
It is taking date as an empty string.
Try defining the empty field as '\N' in your source file.
::DISCLAIMER::
The contents of this e-mail and any
Hi Sergey,
We don't have two-phase commit prepared transactions. During vacuum, along
with this problem we are also facing streaming replication issue. Hundreds
of xlogs are in ready state in pg_xlog/archive_status. Those are being
copied manually after vacuum otherwise rsync happens very slowly a
Hi Venkata,
No there are no other connections to the DB during vacuum.
Regards,
Granthana
On Fri, Mar 21, 2014 at 3:12 AM, Venkata Balaji Nagothi wrote:
> On Thu, Mar 20, 2014 at 5:27 AM, Granthana Biswas wrote:
>
> Hello All,
>>
>> Has anyone ever faced the issue of dead rows not getting remo
27 matches
Mail list logo
